Release Testnet 77, via chain upgrade

[conorsch]

Testnet upgrade

Testnet chain id: penumbra-testnet-deimos-8 (unchanged) Release date: 2024-05-31 Testnet release manager: @conorsch

Testnet Release Manager Checklist

Pre-release:

• [x] Review all merged PRs with tags consensus-breaking and/or state-breaking
• [x] Enumerate the specific PRs that should be included in the release:
  • [x] https://github.com/penumbra-zone/penumbra/pull/4499
  • [x] ECC audit remediation - https://github.com/penumbra-zone/penumbra/pull/4498
  • [x] ECC audit remediation - https://github.com/penumbra-zone/penumbra/pull/4500
• [x] Confirm migrations exist where required for breaking changes already merged
• [ ] Identify specific test cases for before/after behavior, querying chain state, to ensure that migrations are effective
• [x] Prepare upgrade-plan governance proposal
  • [x] Decide on block height at which to halt
  • [x] Double-check you've got bonded stake
  • [x] Submit proposal
  • [x] Vote for it, notify validators of same
  • [x] Confirm proposal passed (default is 4h voting period)

On release day:

• [x] Draft an announcement for peer review to ensure changes included are comprehensive.
• [x] Disable testnet deploy workflow, so that chain is not reset
• [x] Bump the version number and push its tag, via cargo-release.
  • [x] Run cargo release minor for a new testnet, or cargo release patch for a bugfix. For the latter, make sure you're on a dedicated release branch.
  • [x] Push the commit and newly generated tag, e.g. v0.51.0, to the remote.
• [x] Manually trigger container-build workflow, bc deploy workflow is disabled
• [x] Wait for the "Release" workflow to complete
• [x] Edit the newly created release object, and add a note summarizing the intent of the release
• [x] Close faucet (chain halt will make it inoperative anyway)
• [x] Run migrations on all validators
• [x] Run migrations on all fullnodes
• [x] Update Galileo deployment, following docs
• [x] Make the announcement to Discord! 🎉🎉🎉

Post-release cleanup tasks

• [x] Ensure faucet is open
• [ ] Perform Hermes maintenance for genesis restart to get relayer running again
• [ ] Confirm IBC channels are working

[conorsch]

❯ pcli q governance proposal 5 definition
id = "5"
title = "upgrade to 0.77.0"
description = "planned upgrade, via chain migration, to testnet 77"

[upgradePlan]
height = "314250"

[conorsch]

Oops, proposal failed:

❯ pcli q governance proposal 5 state
{
  "finished": {
    "outcome": {
      "failed": {}
    }
  }
}

Will need to reschedule and try again.

[conorsch]

❯ pcli q governance proposal 6 definition
id = "6"
title = "upgrade to 0.77.0"
description = "planned upgrade, via chain migration, to testnet 77 (attempt #2)"

[upgradePlan]
height = "326700"

[conorsch]

Ensure faucet is open

resyncing galileo took ~77m with nearly 400k blocks (and a lot of txs, because it's the faucet). back up and running now.

Perform Hermes maintenance for genesis restart to get relayer running again

We missed this window: during upgrade, the RPC endpoints took a while to restore, and the trusting period elapsed during that maintenance. @avahowell suggested that we modify the unbonding period on the testnet so we get longer trusting periods, widening the time window we have to perform relayer maintenance. That sounds a like a great idea to me. For now, I've created new channels: channel-5 for osmosis testnet and channel-6 for noble testnet.

[conorsch]

For now, I've created new channels: channel-5 for osmosis testnet and channel-6 for noble testnet.

Registry already updated in https://github.com/prax-wallet/registry/commit/3b923ca2a64d043da660c5e978405326c0a4c85d. Closing as complete.