lncm/lnd-rpc
TODO: Describe the point of this repo better
tl;dr
You can:
- download
- generate-go
- generate-python
Each of these is possible in two ways:
- Run the script directly
- Via
docker run
Download all .protos
Run directly
./scripts/download --help
download v1.0.0
Download all .proto files necessary to build lnd's gRPC client libraries
Usage: ./scripts/download [options] LND_VERSION
Where LND_VERSION is in a form: [v]MAJOR.MINOR.PATCH (ex: v0.9.0), or "all" to download all versions
Options:
-h, --help, help Show this help message
-G, --no-google Skip download of google/api/* and google/protobuf/*
-S, --strip-version Don't include lnd version in the path (only works if LND_VERSION != "all")
-o, --output Download to a specified dir (will be created, if doesn't exist)
Examples:
./scripts/download all # Download all lnd versions, and all google/* protos
./scripts/download --no-google v0.4.2 # Only download protos for lnd v0.4.2, and no google/* protos
./scripts/download -G -S -o=~/last-lnd/ v0.9.0 # Only download protos for lnd v0.9.0, and save them to last-lnd/
# in user's HOME directory w/o the /LND_VERSION/ segment in path
github: github.com/lncm/lnd-rpc/
Run in Docker
NOTE: this one requires DOCKER_BUILDKIT=1 due to --target= being used
# Build with:
DOCKER_BUILDKIT=1 docker build . \
--target=protos-downloader
--tag=lnd-rpc-downloader
# Run with:
docker run --rm -it \
--volume=$(pwd)/:/protos/ \
lnd-rpc-downloader # [VERSION|all]
Generate Go
Run directly
./scripts/generate-go --help
generate-go v1.0.0
Compile all .proto definitions into importable .go files
Usage: generate-go [options] LND_VERSION
Where LND_VERSION is in a form: [v]MAJOR.MINOR.PATCH (ex: v0.9.0), or "all" to generate for all versions
Options:
-h, --help, help Show this help message
-S, --strip-version Don't include lnd version in the path (only works if LND_VERSION != "all")
-o, --output Save generated files to a specified dir (created, if doesn't exist)
Examples:
./generate-go all
./generate-go -o /tmp/last/ v0.9.0
github: github.com/lncm/lnd-rpc/
Run in Docker
docker build . \
--build-arg="LANG=go" \
--tag=lnd-rpc-go
docker run --rm -it \
--volume=$(pwd):/data/go/ \
lnd-rpc-go # [VERSION|all]
Metadata
Release files for lnd-rpc 0.4.1.post3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| lnd-rpc-0.4.1.post3.tar.gz | 30.2 kB | Without provenance | Details for lnd-rpc-0.4.1.post3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| lnd_rpc-0.4.1.post3-py3-none-any.whl | Python 3 | none | any | Details for lnd_rpc-0.4.1.post3-py3-none-any.whl |
Total release size: 61.3 kB
Release files / lnd-rpc-0.4.1.post3.tar.gz
| Download URL | lnd-rpc-0.4.1.post3.tar.gz |
|---|---|
| Size | 30.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
975bd4801d96d40f31cd077bc0827c1d813e995578cfa18b85d78df04f973034
|
|
BLAKE2b-256 checksum How to use checksums |
d91b43a93c4b68939c73660bafcdcb78ac6ab22c3d9ada0ac1b3790612957a6a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.22.0 setuptools/45.1.0 requests-toolbelt/0.9.1 tqdm/4.42.1 CPython/3.8.1
|
Release files / lnd_rpc-0.4.1.post3-py3-none-any.whl
| Download URL | lnd_rpc-0.4.1.post3-py3-none-any.whl |
|---|---|
| Size | 31.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f75a318141dffcd72e494e8fed79376f12721fcb7ab2c50685d6fdee5c8da014
|
|
BLAKE2b-256 checksum How to use checksums |
f77ff78c4121ea554105e589083500c086b8896c484ccc3a196a3a1e0590a008
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.22.0 setuptools/45.1.0 requests-toolbelt/0.9.1 tqdm/4.42.1 CPython/3.8.1
|
Security for lnd-rpc 0.4.1.post3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.