This post is being updated along with the project progress. Last Update (25th June 2017)
|Description||A minimal command-line tool to help start building Dapps for Ethereum|
I’ve had my share of trouble getting started with building Distributed apps (Dapps) on Ethereum. There are a bunch of frameworks out there like this and this that help get started immediately. But these frameworks did way too much by themselves. I wanted to understand every step involved in deploying contracts, generating their ABIs, and using them in Dapps through JSON RPC. This prompted me to build
Wait, is this another framework?
I wouldn’t call it a framework. Wasabi does the following few things.
- Sets up a minimal project structure with directories for contracts, app and config.
- Compiles contracts and provides an estimate of gas consumption provided by the configured RPC node.
- Deploys contracts using transaction signature at node OR on client.
- Creates a JSON file with Contract addresses and ABIs.
What does it not do?
- It does not have testing inbuilt. As far as possible, everything in the
/appdirectory is to be owned by the web developer. This provides freedom to use development and testing frameworks of their choice.
- Does not maintain contract compile/migration history.
Can I start using wasabi for a project that I plan to take in to production?
NO. Not yet. I am building wasabi to suit my own selfish needs, and introduce myself to the intricate art of publishing contracts and integrating them in web apps. While I do plan to make this ready for production, at this moment I provide no garauntees that the tool will work as expected.
Can I use it for projects which I don’t mind buring down to ashes?
Sure. If you are learning or experimenting with Ethereum, please feel free to use wasabi and hit me with any feedback with how well or how badly it worked for you. I’ll be glad to accept feedback in terms of issues, feature request and better yet, pull requests.