AstarNetwork/Astar

Move genesis config in runtime and organize variants with presets

ipapandinas opened this issue · 2 comments

Description

Moving genesis config from the node into the runtime improve decoupling between the two.
This can be organized in a similar convention as changes introduces in paritytech/polkadot-sdk#2714:

Required Tasks

  • Create a genesis_config_presets.rs file per runtime that contains helpers for the GenesisBuilder API
  • Implement 3 presets: "live", "local_testnet" & "development"

@ipapandinas I just noticed this issue. Didn't know you've created it last week 😄

This is (mostly) resolved by this PR: #1341

However, I'm not sure what would be the difference between the listed types?

After reviewing your PR, only the "development" preset coupled with tokyo testnet is relevant ✌️