lord kelvin
EVM interface
Quickstart:
- to just build the docker image, type:
make dbuild
- to run tests, type:
make -C tools
- or to use a specific ganache port:
PORT=1234 make -C tools
- to run tests, then get a shell, type:
make -C tools sh
- or to use a specific ganache port:
PORT=1234 make -C tools sh
Using different networks
-
Only
ganacheandkovanare supported -
To add a network:
-
- add a new
env.{NEWORK}.shfile to tools
- add a new
-
- add a new alias in
tools/aliases
- add a new alias in
Inside docker
-
your life is easy, just type the name of the network!
-
Examples:
ganache
kovan
Outside docker
- to use ganache (the default), type:
source env.sh
- to use kovan, type:
source env.kovan.sh
Metadata
Release files for lordkelvin 4.4.4
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 |
|---|---|---|---|---|
| lordkelvin-4.4.4.tar.gz | 16.0 kB | Without provenance | Details for lordkelvin-4.4.4.tar.gz |
Release files / lordkelvin-4.4.4.tar.gz
| Download URL | lordkelvin-4.4.4.tar.gz |
|---|---|
| Size | 16.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
dc401b1e40c0f02f08c5da952e7ac27165bfc2ea03e08ddf4f01652f1b02dd65
|
|
BLAKE2b-256 checksum How to use checksums |
b6c3458ab651bbf683fd01033d4cf69c923c077d1f465c53c730b025079faafe
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.2 importlib_metadata/3.10.0 pkginfo/1.7.1 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.53.0 CPython/3.9.10
|
Security for lordkelvin 4.4.4
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.