The README file contains a lot of code examples, which tend to get outdated pretty quickly as the API is still undergoing some changes.

It would be nice to keep these code samples in the project codebase (in an examples folder...?), have them all properly unit-tested and dynamically included into the documentation - not necessarily into the README file - so we are sure all of them are always

When running pip3 install -r requirements.txt with pip 18, I get this warning:

eth-keys 0.2.0b3 has requirement eth-utils<2.0.0,>=1.0.0-beta.2, but you'll have eth-utils 0.7.1 which is incompatible.
eth-keyfile 0.5.1 has requirement eth-utils<2.0.0,>=1.0.0-beta.1, but you'll have eth-utils 0.7.1 which is incompatible.
eth-tester 0.1.0b32 has requirement eth-utils<2.0.0,>=1.0.1, but you

User feedback from Dappy Hour: "Why do I want to become a vendor? I just want to start accepting crypto as easy as cash."

"Become a Vendor" assumes that a visitor knows that they want to become a vendor. If the text said something like 'Begin' or 'S

Some gas estimation tests are ignored by solidity-coverage in CI via the @skip-on-coverage tag (using mocha -g). However, it is important that these tests are run via truffle test. At the moment, we have to put the test in a separate file and run truffle test on this separate file.

Truffle currently has an open issue trufflesuite/truffle#2080 that would help ensure that no tests are acc

Type:

Request

What do you need?:

We need to alert the user in some way (console) that he was removed from the consensus elections.

Priority:

Low

Other info we may need:

Possible related issue #140
Depends on #136