solc

deploying libraries can take a long time. One can easily skip this stage if we make it possible to save the deployed library state and pass it to dapp test:

1. Write a new little dapp helper script which is the dapp --library-addresses above
2. Make dapp build and dapp --make-library-state use this helper script instead
3. Allow a flag --state to be passed to dapp test (probably a

What was wrong?

The error message is not clear, when solc isn't available.

Examples:

• https://ethereum.stackexchange.com/questions/26192/errno-2-no-such-file-or-directory-solc-using-py-solc-and-solidity
• ethereum/web3.py#467

Proposal: catch and reraise the exception with a note saying something like:

The command line tool solc wasn't found. Try `

Substitute the web3j code generator for a similar code generator that emits Scala code instead of Java code.

Currently the only tests are running against Aragon and OpenZeppelin's contracts. This is a good general test that nothing is broken, but it's hardly the proper fine-tuned approach that unit tests should take. Also, significant amounts of the code aren't touched by it.

This project isn't very big, it shouldn't take much work to get coverage in the mid 90's.

https://github.com/tonsoft/homebrew-stable/pulls?q=is%3Apr+is%3Aclosed+label%3Abottle