-
Notifications
You must be signed in to change notification settings - Fork 296
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
upgrades: testnet rollover between 60 and a private fork #2917
Comments
This is currently blocked on #2967 |
We are optimistic about merging #2981 for Testnet 60. Our plan for 60 is not to engage the community validators and require them to participate, but rather to fork the network into a private devnet, and run the upgrade logic there. That will enable us to exercise the upgrade logic for the first time, identify and issues, and target a future testnet (61?) for a community-run upgrade process. |
Another item we will want to test during the rollover is whether we confirmation that we can get a tendermint light client to verify across the upgrade boundary. This is an important goal of the upgrade story because it would mean that we do not need to patch penumbra light clients on counterparty chains, unless we deliberately change their client state (e.g. client id). |
@conorsch and I were able to test this successfully, here are the (notes from the test). During next testnet we want to exercise the updated upgrade flow that completely resets the consensus state and takes advantage of new checkpointed genesis format. |
Part of #1804, stub.
The text was updated successfully, but these errors were encountered: