The comments around from_seed_slice specify that this is a dangerous method only to be used for testing, however the upper of Pair uses it without that information passed on and the client is using the same functionality to generate the tests keys for Alice, Bob, etc.

We should clarify the documentation to clearly stated under which circumstances this features is to be expected to be us

The install instructions currently result in an old version (1.0.1) of the generator being installed which is inconsistent with the rest of the documentation.

We need to alter the docs or update the nuget.

https://github.com/Nethereum/Nethereum/tree/master/src/Nethereum.Generator.Console

There is a small bug in the documentation. In 3.2. Local Two-node Testnet, the commands should be ./polkadot --chain=local --alice -d /tmp/alice and ./polkadot --chain=local --bob -d /tmp/bob --port 30334 --bootnodes /ip4/127.0.0.1/tcp/30333/p2p/ALICE_BOOTNODE_ID_HERE since the option --key is not recognized

client.transfer method currently always sets data in transaction to be a blank string. This should be added as (optional?) method argument.

The result of simply doing npm install

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! react-redux-universal-hot-example@0.1.0 postinstall: concurrently "npm run build" "npm run build-dlls"
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the react-redux-universal-hot-example@0.1.0 postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional log

Also, actually add missing docs as the result.

Also, deny warnings on the CI (but it does not work well with cargo workspaces atm).

Feedback from a user:
At Parity we use foundation to talk about the main ETH network since the beginning. Out there, it's called "Mainnet" and we should probably call it that way in the UI to make sure it's not confusing anyone.

Currently we use RwLock<Option<DBAndColumns>> in order to:

• support closing/upgrading (see restore) a RocksDB kvdb database.
• [hold a read lock](

Is your feature request related to a problem? Please describe.
There are many ways to read and write root trees (from JAPAN or otherwise), as well as EPICs data (reading and writing - for stripcharts and alarm handling), and if we could keep all of that information together and in a concise set of examples that would be really helpful.

Describe the solution you'd like
A wiki section i