You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now, we have a single config file (config.toml by default) containing a number of sections. Some of these sections contain data that the node operator can update at-will, e.g., NTP server list, API config, and logging section. Some sections should not be updated unilaterally by a node operator but could conceivably change in a coordinated fashion post-genesis, e.g., HARE config. Other sections contain things that can never change post-genesis, e.g., main.genesis-time and main.golden-atx, and the entire genesis section (containing genesis accounts and balances). Some of the beacon and tortoise sections of the config should probably not be able to change after genesis, we need to double check this. (For now, we'll leave alone the second class of config items, those that should not be updated unilaterally; we may want to revisit this in future.)
The task: split out immutable, genesis-related config items from the main BaseConfig object and move them into the Genesis config object. Split this from config.toml and move it into a new standalone genesis.toml file.
Every time the node starts, check that the genesis config has not changed (and panic/refuse to start if it has): this may involve saving a hash of the config to the database, something along these lines.
Description
Right now, we have a single config file (
config.toml
by default) containing a number of sections. Some of these sections contain data that the node operator can update at-will, e.g., NTP server list, API config, andlogging
section. Some sections should not be updated unilaterally by a node operator but could conceivably change in a coordinated fashion post-genesis, e.g., HARE config. Other sections contain things that can never change post-genesis, e.g.,main.genesis-time
andmain.golden-atx
, and the entiregenesis
section (containing genesis accounts and balances). Some of thebeacon
andtortoise
sections of the config should probably not be able to change after genesis, we need to double check this. (For now, we'll leave alone the second class of config items, those that should not be updated unilaterally; we may want to revisit this in future.)The task: split out immutable, genesis-related config items from the main
BaseConfig
object and move them into theGenesis
config object. Split this fromconfig.toml
and move it into a new standalonegenesis.toml
file.Every time the node starts, check that the genesis config has not changed (and panic/refuse to start if it has): this may involve saving a hash of the config to the database, something along these lines.
Affected code
See also:
GENESISID
pm#135This issue appears in commit hash: 5eb9998
The text was updated successfully, but these errors were encountered: