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

State Export Logic Audit #2940

Closed
Tracked by #4622
czarcas7ic opened this issue Oct 4, 2022 · 1 comment
Closed
Tracked by #4622

State Export Logic Audit #2940

czarcas7ic opened this issue Oct 4, 2022 · 1 comment

Comments

@czarcas7ic
Copy link
Member

czarcas7ic commented Oct 4, 2022

Background

If it ever came down to needing a new genesis file for mainnet, we need to be certain that the current state export logic created a genesis file that replicated mainnet 1:1. As it stands, we have had to make many changes over the months after realizing things were left out or were incorrect in osmo-test-4 due to improper state export logic.

Suggested Design

Go through every module and ensure state export logic is sound.

We can even make a new testnet (osmo-test-5) to be the new main testnet, and we can query various things on this testnet and see if there is anything off in terms of what should have been exported and what really was exported.

Acceptance Criteria

Every module has been checked against a running testnet to verify all state export logic is sound.

@ValarDragon
Copy link
Member

Unneeded due to in place testnet

@github-project-automation github-project-automation bot moved this from Needs Triage 🔍 to Done ✅ in Osmosis Chain Development Feb 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

No branches or pull requests

2 participants