Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add automatic state dump post-processing to make it usable as a Genesis document #2886

Open
tjanez opened this issue May 5, 2020 · 0 comments
Labels
c:consensus/cometbft Category: CometBFT

Comments

@tjanez
Copy link
Member

tjanez commented May 5, 2020

SUMMARY

Currently, the state dump to a genesis file obtained via oasis-node genesis dump sub-command may produce a Genesis document with which a network cannot be started without manual post-processing.

Adding (optional) automatic state dump post-processing would make the state dump more convenient to use since it could be readily used to start a new network (e.g. on a dump-and-restore network upgrade cycle).

ISSUE TYPE
  • Feature Idea
ADDITIONAL INFORMATION

The post-precessing is needed to remove entity, node and runtime registrations for which the corresponding entity doesn't have enough stake escrowed anymore, but they haven't been removed from network's state yet since that only occurs on epoch transitions.

This is a follow-up from #2748 which augments registry's staking sanity checks to check if an entity has enough stake for all stake claims in the Genesis document to prevent panics at oasis-node start-up due to entities not having enough stake in the escrow to satisfy all their stake claims.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
c:consensus/cometbft Category: CometBFT
Projects
None yet
Development

No branches or pull requests

1 participant