Solidity development tools for creating Ethereum smart contracts
Project description
solidbyte
Development tools for creating Ethereum smart contracts.
Curious what a Solidbyte project looks like? Check out the solidbyte-test-project repository.
What makes Solidbyte different?
- Local accounts - Solidbyte can use the local accounts stored as Ethereum secretstore files located at
~/.ethereum/keystore. You do not need to trust the node you are using to handle your private keys and risk opening your account withpersonal.unlock. - Python! - Deploy scripts and tests are written using Python.
- EthPM support - Well, it's in progress and not usable yet, but... it probably will be at some point.
- Vyper and Solidity support - Contracts written in either language can co-exist side by side with eachother in your project.
- Interactive python console - Solidbyte provides a console with an insantiated Web3 object and your deployed contract instances. Have I mentioned Python yet?
- Projcet templates - You can initialize a project template with a single command that includes example deploy scripts, tests, and contracts. Right now only 'bare' and 'erc20' templates are available, but I hope to add more.
- Contract testing with pytest - Pytest is used for contract testing with some provided fixtures. Something something Python.
- eth_tester support for testing - It's super fast and really useful for first-pass testing.
NOTE: Solidbyte has only been tested on Linux. If you use another OS, please consider testing and submit an issue for any bugs you find.
What's in the future?
See the roadmap.
Demo
Here's a brief demo (as of 2019-03-25) creating a new ERC20 token named MyToken:
Contents
Quickstart
1) Install Solidbyte
Solidbyte requires some system-level libraries to be installed first. Make sure openssl/libssl and libffi headers are installed before proceeding. For more information, see the longer installation docs.
First, install solidbyte. The easiest way to do that is from PyPi
with pip.
pip install solidbyte
2) Setup your project
To get your project going, create a directory for your project and change to it.
Most sb commands need to be run from the root of your project directory.
mkdir myproject && cd myproject
sb init
Now, all you should have a bare project structure created. You could also
init with an available template,
but for the purposes of this doc, we're just going to create a bare structure.
Your contracts should be in the contracts directory. Your Solidity or Vyper
contracts can be in any directory under it.
The deploy directory will hold your deployment scripts.
And tests will contain your contract unit tests.
The build directory probably doesn't exist yet. This will be created by
solidbyte when necessary.
You can also create scripts to be run by Solidbyte in the scripts directory.
They must be implemented according to the documentation.
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
File details
Details for the file solidbyte-1.1.0b3.tar.gz.
File metadata
- Download URL: solidbyte-1.1.0b3.tar.gz
- Upload date:
- Size: 2.3 MB
- Tags: Source
- Uploaded using Trusted Publishing? No
- Uploaded via: twine/3.2.0 pkginfo/1.5.0.1 requests/2.24.0 setuptools/50.3.0 requests-toolbelt/0.9.1 tqdm/4.49.0 CPython/3.8.0
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 | 1bdd30c11b9bf584fedd64b77fceb45da534b016292ffb28e2b38c7f66aa6e51 |
|
| MD5 | 8e64d47c71cfe718025d2712a26429a6 |
|
| BLAKE2b-256 | 1c7e127ebfbc431ef79ced657e3bf879517f9e12ab3fd1b295db6bb5d8788a41 |
