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
I propose to add a flag to the simd init command, that controls the default starting block height of the output genesis.json
Problem Definition and Proposal
I am frequently spinning local testnets with multiple validators for the blockchain that I am working on. On softforks of the codebase the behavior of these testnets happen to be block height dependent. This comes with the extra burden of creating tooling around modifying the genesis.json after simd init. It feature would not add any "value" to Cosmos SDK. It's just a neat feature. Nice to have. And I am totally happy to implement this on my own. So, please, assign to me.
The text was updated successfully, but these errors were encountered:
Thanks for opening this issue, we can accommodate this feature. It makes me think if we should add a genesis modification tool to the tools directory since many people have scripts
Summary
I propose to add a flag to the
simd init
command, that controls the default starting block height of the outputgenesis.json
Problem Definition and Proposal
I am frequently spinning local testnets with multiple validators for the blockchain that I am working on. On softforks of the codebase the behavior of these testnets happen to be block height dependent. This comes with the extra burden of creating tooling around modifying the
genesis.json
aftersimd init
. It feature would not add any "value" to Cosmos SDK. It's just a neat feature. Nice to have. And I am totally happy to implement this on my own. So, please, assign to me.The text was updated successfully, but these errors were encountered: