uses 'ezdev' as --chain val, setting chaindata dir and other
related configuration and resource paths
creates 10 accounts if keystore/ dir does not contain keyfiles
sets respectable balance for each of these accounts in the genesis
block, then writing the genesis config file and other config files
to the chaindata dir
creates AUTOMINING feature for miner, where addition of a transaction
to the txpool spawns a block win, which, with the automine config, is
set to bypass the nonce+mixhash header validations normally done for ethash
validations.
turns on --lightkdf--mine and --no-discover
You can still use --keystore flag to specify the directory that should contain key files. You can still use --sputnikvm. You can still use the --datadir flag.
The only real opinion here is that the --ezdev flag overrides the --chain=ezdev flag.
If you want to tinker with the config vals, take a look at the chain.json config file; you'll find that either in <datadir>/ezdev/chain.json or with geth --ezdev dump-chain-config chain.json.
Creates flag --ezdev which
--lightkdf--mineand--no-discoverYou can still use
--keystoreflag to specify the directory that should contain key files. You can still use--sputnikvm. You can still use the--datadirflag.The only real opinion here is that the
--ezdevflag overrides the--chain=ezdevflag.If you want to tinker with the config vals, take a look at the
chain.jsonconfig file; you'll find that either in<datadir>/ezdev/chain.jsonor withgeth --ezdev dump-chain-config chain.json.