Genesis file should be dynamic, not baked in about lunie HOT 4 CLOSED

I think we should have this as a convention:

npm run development - starts a local testnet
npm run testnet - connects to a remote testnet, later on you can specify which testnet through a flag
npm run mainnet - connects to a remote mainnet

from lunie.

And the genesis files for each, except the development, one should be in the binary, so that users don't have to deal with separate genesis files.

The development genesis file should live in the repository and a user should be able to update it.

The same applies to keys with money.

Example 1

A user runs npm run development. The genesis file from the file system gets taken and keys with a lot of default money are written into the correct directory. After that command a user can immediately start to use the UI without having to copy any other files.

Example 2

A user runs npm run mainnet. The UI is initialised with the correct genesis file without user interaction and the UI starts syncing with the mainnet.

from lunie.

On the testnets branch, I implemented npm run testnet [network] and npm run local.

@adrianbrink I like your idea of managing the keys for local testnets to make it easier to start with coins, I'll add that next.

from lunie.

Done as of f1fa74d. Now npm run local will start a local testnet, with your client credited with a large balance of coins.

from lunie.