Proposals of #9

Upgrade v5 PersistenceCore

Exec Legacy Content
passed
Expected result
Turnout / Quorum
49.63% / 40.00%
Voting start 2022.11.15 at 19:11:52
Voting end 2022.11.22 at 19:11:52
100.00%
68 551 052 xprt
Yes
0%
0 xprt
No
0%
0 xprt
Veto
0.00%
645 xprt
Abstain

Details

Proposer
-
Total deposit
512 xprt
Submit time
2022.11.15 at 15:11:38
Deposit end time
2022.11.29 at 15:11:38

Description

Persistence v5\n\nThis is a proposal to do a software upgrade to the v5.0.0 software tag of the Persistence codebase on block height 8910100, which is estimated to occur on 8910100. Block times have high variance, so please monitor\nthe chain for more precise time estimates.\n\n## Upgrade Features\nThis upgrade adds the following features:\n\n### pstake-native v1.2.0\n* Ablity to reopen IBC channels for ICA/ICQ on channel close as a txn\n\n### Fail previous claims: Upgrade Handler\n* Upgrade handler code to fix the state of mainnet due to ICA channel close\n\n### Others\n* Upgrade cosmos-sdk to v0.45.10\n* Upgrade IBC-go to v3.4.0\n* Upgrade pstake-native v1.2.0\n* Upgrade tendermint to v0.34.22\n\nFull Change Log\n\n## Getting Prepared for the Upgrade\n\nAs always, we recommend validators utilize 64GB of RAM. Since state migration is relatively negligible in this upgrade, it is likely possible to get away with less, but still not recommended. If you are unable to have 64GB of RAM, at a minimum have a total of 64GB of swap set to prevent out of memory errors.\n\nIf using cosmovisor, manually build & copy the persistenceCore binary to /cosmovisor/upgrades/v5/bin/.\n\nIf not using cosmovisor, wait for your node to halt at the upgrade height, then install and run the v5.0.0 binary.\n\nNote: Please use go version as part of v5 upgrade\n\n\n## Details of Upgrade Time\n\nThe proposal targets the upgrade proposal block to be 8910100. Note that block times have high variance, so keep monitoring the time. See countdown here.\n\nThe upgrade is anticipated to take approx 30 minutes, during which time, there will not be any on-chain activity on the network.\n\nIn the event of an issue at upgrade time, we should coordinate via the validators channel in discord to come to a quick emergency consensus and mitigate any further issues.\n

Votes

Voter
Answer