core: added basic chain configuration
Added chain configuration options and write out during genesis database insertion. If no "config" was found, nothing is written to the database. Configurations are written on a per genesis base. This means that any chain (which is identified by it's genesis hash) can have their own chain settings.
Showing
- accounts/abi/bind/backends/simulated.go 8 additions, 3 deletionsaccounts/abi/bind/backends/simulated.go
- cmd/ethtest/main.go 3 additions, 2 deletionscmd/ethtest/main.go
- cmd/evm/main.go 11 additions, 8 deletionscmd/evm/main.go
- cmd/geth/js_test.go 1 addition, 0 deletionscmd/geth/js_test.go
- cmd/geth/main.go 39 additions, 3 deletionscmd/geth/main.go
- cmd/geth/usage.go 1 addition, 0 deletionscmd/geth/usage.go
- cmd/utils/flags.go 53 additions, 19 deletionscmd/utils/flags.go
- common/debug.go 16 additions, 0 deletionscommon/debug.go
- common/registrar/ethreg/api.go 16 additions, 4 deletionscommon/registrar/ethreg/api.go
- core/bench_test.go 1 addition, 1 deletioncore/bench_test.go
- core/block_validator.go 17 additions, 15 deletionscore/block_validator.go
- core/block_validator_test.go 9 additions, 3 deletionscore/block_validator_test.go
- core/blockchain.go 10 additions, 15 deletionscore/blockchain.go
- core/blockchain_test.go 18 additions, 17 deletionscore/blockchain_test.go
- core/chain_makers.go 23 additions, 4 deletionscore/chain_makers.go
- core/chain_makers_test.go 1 addition, 1 deletioncore/chain_makers_test.go
- core/config.go 46 additions, 0 deletionscore/config.go
- core/database_util.go 34 additions, 0 deletionscore/database_util.go
- core/execution.go 1 addition, 1 deletioncore/execution.go
- core/genesis.go 14 additions, 9 deletionscore/genesis.go
Loading
Please register or sign in to comment