PersistenceCore v16.1.0

Original Proposal Text

# Persistence Core-1 v16.1.0 Security Upgrade This proposal schedules a coordinated software upgrade of Persistence `core-1` to **`v16.1.0`** at height **`29376200`**, expected around **Thursday, 24 September 2026, 14:00 UTC**. Block times have high variance, so please monitor the chain for the precise halt time. **This upgrade is state-breaking and mandatory** once the on-chain vote passes and the upgrade height is reached. ## Release details Due to the sensitive nature of this patch: - There will be **no public GitHub release** before the upgrade. - The `info` field of this upgrade plan is intentionally empty. Binaries will **not** be published for Cosmovisor auto-download. - **Only prebuilt binaries** will be available until the private disclosure period ends and all affected chains have been patched. - The Persistence team will **distribute binaries privately** to validators and node operators. - Source code will be published after the coordinated disclosure window closes. - **Node operators should NOT expect to build this from source before the upgrade.** Use the privately distributed official binary. Place the provided `persistenceCore` binary in: ``` $HOME/.persistenceCore/cosmovisor/upgrades/v16.1.0/bin/persistenceCore ``` Operators upgrading manually should halt at height `29376200` and replace the binary with the privately distributed `v16.1.0` binary before restarting. ## Communications Operators are encouraged to join the `#validators-discussion` channel of the Persistence Community Discord. This channel is the primary communication tool for operators to receive the binary, ask questions, report upgrade status, report technical issues, and build social consensus should the need arise. If you don't have access, please contact someone from the Persistence team directly. ## Governance votes YES - You agree that Persistence should be upgraded to `v16.1.0` at height `29376200`. NO - You disagree that Persistence should be upgraded with this release. NO WITH VETO - A `NoWithVeto` vote indicates a proposal either (1) is deemed to be spam, i.e., irrelevant to Persistence, (2) disproportionately infringes on minority interests, or (3) violates or encourages violation of the rules of engagement as currently set out by Persistence governance. ABSTAIN - You wish to contribute to the quorum but you formally decline to vote either for or against the proposal.