Proper GenesisConfig

[PopcornPaws]

Description

Once the chain is up and running, and available to a wider audience, we cannot just stop, recompile and restart the chain. We would need to operate with runtime upgrades from that point on, which requires some preparation. To be honest, we should start working with runtime updates as soon as possible to become comfortable with the process, see #87 for more details.

Since runtime upgrades require root access, we should specify an admin key in the sudo pallet at genesis. This can be set in gn-node/src/chain_spec.rs. For this we should generate an admin key that's only known to us. In case we want to reassign sudo privileges to another account, the sudo pallet has the set_key method just for that purpose. We could even set it to the zero address if we want.

We should also generate 3 initial proof-of-authority keys as validators and maybe a faucet.

Solution

• generate an admin key and add it to the Sudo genesis config and premint some tokens for it
• generate 3 initial validator keys and premint some tokens for them
• generate a faucet and premint lots of tokens for them
• store the validator keys in the keystore (automatically?)
• figure out how new validators can join the chain #103

[PopcornPaws]

How to add new validators?

• https://stackoverflow.com/questions/61883812/how-to-add-remove-validators-in-a-substrate-network
• https://substrate.stackexchange.com/questions/198/how-do-you-add-new-validators-for-your-blockchain-testnet
• https://decentration.medium.com/set-up-public-relay-validators-with-a-partner-3ef409c675c7

Steps:

• add the session-pallet
• or use this