Contracts Deploy Tool
This deploy tool can be used to deploy contracts of this repository on a blockchain and interact with them. To read more about the contracts, readme the root directory readme
Installation
You can install the deploy tool from this directory by running:
pip install -r requirements.txt -e .
You can otherwise install it by running
pip install trustlines-contracts-deploy
You can verify proper installation by running tl-deploy --help, which should bring up the help for the tool.
Usage
There are 4 main commands for tl-deploy: currencynetwork, exchange, identity-implementation,
and identity-proxy-factory. There is also a command test that combines deployment of the previous contracts
used for testing purposes.
Different commands have different options depending on the specific contracts they deploy.
You can see these options by running the help on the command, e.g. tl-deploy currencynetwork --help.
However all the commands will:
- need to connect to a blockchain node with option
--jsonrpc, - use gas price set with
--gas-price - use custom gas limit if set with
--gas - start with nonce set by
--nonceor use the last nonce of sender if--auto-nonceis set - get access to a keystore file via
--keystore
1 maintainer
Metadata
1 maintainer
Release files for trustlines-contracts-deploy 2.0.0
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 | |
|---|---|---|---|---|
| trustlines-contracts-deploy-2.0.0.tar.gz | 21.3 kB | Without provenance | Details |
Release files / trustlines-contracts-deploy-2.0.0.tar.gz
| Download URL | trustlines-contracts-deploy-2.0.0.tar.gz |
|---|---|
| Size | 21.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5606a0d1670e8e3075bb3550ff906fec307ad7f4fb17a50b028ab21483392147
|
|
BLAKE2b-256 checksum How to use checksums |
ae3e9de244fca0d9bf531e5a59c6fc84385801d8b40447a8dcbccb0ac85d4935
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.3.0 pkginfo/1.7.0 requests/2.25.1 setuptools/54.0.0 requests-toolbelt/0.9.1 tqdm/4.58.0 CPython/3.6.9
|
Security for trustlines-contracts-deploy 2.0.0
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.
