Python implementation for terra.proto
This is a version of terra.proto which specifically supports Terra Classic.
It is intended to be a drop-in replacement for terra.proto - it will install itself as terra.proto.
This is required if you are using the Terra Classic SDK.
Build instructions
Requirements:
python -m pip install "betterproto[compiler]==2.0.0b6"
brew install protobuf
Steps
Download the 50.x version of terra.proto. You can replace the branch name with whatever is relevant.
git clone -b v0.50.x-support https://github.com/geoffmunn/terra.proto.git
Alongside this, download the current version of terra/core from terra-money
git clone https://github.com/terra-money/core.git terra/
If terra/ already exists, then delete it with this: git rm -r terra
Move into the terra.proto directory and add the submodules
cd terra.proto
git submodule add https://github.com/classic-terra/core terra/
git submodule update --init
cd terra/
git checkout 680792d
[!IMPORTANT] 680792d is the commit ID of the terra branch we want to use (not 'main'). Replace this with the version you are interested in.
Now copy from the terra-money terra location the following files into the terra.proto/terra/proto location:
cd ./proto
cp -r ../../../terra/proto/cosmos .
cp -r ../../../terra/proto/juno .
cp -r ../../../terra/proto/osmosis .
Move to the scripts location to start the build process
cd ../../python/scripts
rm -rf ../terra.proto (location may not exist, ok if it doesn’t)
sh proto-gen.sh
AFTER RUNNING THE PROTO BUILD SH FILE:
cp -r ./gamm-files/ ../terra_proto/osmosis/
Finished! You can run the python module build steps from here.
Alternative options to this library can be found here:
- GoLang Terra Core clients,
- JavaScript @terra-money/terra.proto,
- Rust terra-proto-rs.
Metadata
Release files for terra-classic-proto 4.0.1
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 | |
|---|---|---|---|---|
| terra_classic_proto-4.0.1.tar.gz | 237.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| terra_classic_proto-4.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 585.7 kB
Release files / terra_classic_proto-4.0.1.tar.gz
| Download URL | terra_classic_proto-4.0.1.tar.gz |
|---|---|
| Size | 237.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
21965857b1e9067f4c2213c6be695c640e6d95b695dbf1c34e2e5b0fc3ab9388
|
|
BLAKE2b-256 checksum How to use checksums |
a668447b9204a701c595eb277af942f73c60eed5e6001adcebc241ea9303b5e0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.9
|
Release files / terra_classic_proto-4.0.1-py3-none-any.whl
| Download URL | terra_classic_proto-4.0.1-py3-none-any.whl |
|---|---|
| Size | 348.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
10e1e7aca161a19726672bf179d20fc0ea76a48cac5a533c0e4b5915dd87101d
|
|
BLAKE2b-256 checksum How to use checksums |
82cee545837577eb77272bfcdc6959733779512e26f62234ee26847246b8adc7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.9
|
Security for terra-classic-proto 4.0.1
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.