Release Testnet 78, via chain upgrade

[conorsch]

Testnet upgrade

Testnet chain id: penumbra-testnet-deimos-8 (unchanged)
Release date: 2024-06-25 (?)
Testnet release manager: @conorsch

Testnet Release Manager Checklist

It's been over a week since the chain upgrade from 76 -> 77 (#4497), so let's schedule another. We plan to ship the entirety of main, to flush out all pending changes. As usual, special attention must be paid to breaking changes, which require writing migrations.

Pre-release:

• Review all merged PRs with tags consensus-breaking and/or state-breaking
• Enumerate the specific PRs that should be included in the release:
  • Enforce string limits for deserialization #4567 (and follow ups)
  • dex: fold Positions into the price indexes #4564
  • dex: make the execution budget a chain parameter #4602
  • zellic audit remediations ibc-types#88
  • feat(crypto): add phase 2 outputs from ceremony #4661
  • PR to bump ibc-types version (TK)
  • Handle the CometBFT block size changes (either via announcement ask or automated config munging) that were made in pd: use 10MB as mempool limit in comet config template #4594
• 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
• Prepare upgrade-plan governance proposal
  • Decide on block height at which to halt
  • Double-check you've got bonded stake
  • Submit proposal
  • Vote for it, notify validators of same
  • Confirm proposal passed (default is 24h voting period)

On release day:

• Draft an announcement for peer review to ensure changes included are comprehensive.
• Disable testnet deploy workflow, so that chain is not reset
• Bump the version number and push its tag, via cargo-release.
  • 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.
  • Push the commit and newly generated tag, e.g. v0.51.0, to the remote.
• Manually trigger container-build workflow, bc deploy workflow is disabled
• Wait for the "Release" workflow to complete
• Edit the newly created release object, and add a note summarizing the intent of the release
• Close faucet (chain halt will make it inoperative anyway)
• Run migrations on all validators
• Run migrations on all fullnodes
• Update Galileo deployment, following docs
• Make the announcement to Discord! 🎉🎉🎉

Post-release cleanup tasks

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

[conorsch]

❯ pcli tx proposal submit --file 78-upgrade.toml  --deposit-amount 10penumbra
Scanning blocks from last sync height 723008 to latest height 723009
[0s] ██████████████████████████████████████████████████       1/1       12/s ETA: 0s
building transaction [4 actions, 3 proofs]...
finished proving in 0.553 seconds [4 actions, 3 proofs, 2496 bytes]
broadcasting transaction and awaiting confirmation...
transaction broadcast successfully: 79760d4374c3e650b04b18bd184ebe6f07539aad9f9eef590e10955a40b43cdc
transaction confirmed and detected: 79760d4374c3e650b04b18bd184ebe6f07539aad9f9eef590e10955a40b43cdc @ height 723010

❯ pcli q governance proposal 13 definition
id = "13"
title = "upgrade to 0.78.0"
description = "planned upgrade, via chain migration, to testnet 78"

[upgradePlan]
height = "734700"

[conorsch]

❯ pcli q governance proposal 13 state
{
  "finished": {
    "outcome": {
      "passed": {}
    }
  }
}

[conorsch]

Testnet 78 shipped yesterday https://github.com/penumbra-zone/penumbra/releases/tag/v0.78.0, and it was good.