Persistence One

Restaking

Proposal Details

Proposal #12

Passed

Proposal title

Upgrade v6 PersistenceCore

Submit time

Deposit end time

Voting start time

Voting end time

Tally result

97.66%

Proposal #12 description

Persistence v6

This is a proposal to do a software upgrade to the v6.0.0 software tag of the Persistence codebase on block height 9601000, which is estimated to occur on 12:11 PM GMT, 11th Jan 2023. Block times have high variance, so please monitor the chain for more precise time estimates. Please check the exact time on the countdown

Upgrade Features

This upgrade adds the following features:

Untombstoning

v6 upgrade will untombstone and unslash validators which were tombstoned on the v5 upgrade process. Please check proposal 10 for more details.

Fix pSTAKE c-value

Upon testing of stkATOM on Persistence mainnet prior to launch, an edge-case that skews the c-value or the exchange rate between stkATOM/ATOM drastically was found. This upgrade fixes that by minting new stkATOM against the ATOM deposited to the Reward rate ICA account (which is what caused the exchange rate to jump from 1 to 1.67). This would reset the exchange rate to 1 and result in a greater user experience at launch for pSTAKE.

Others

  • Upgrade cosmos-sdk to v0.45.11
  • Upgrade cosmos IAVL to v0.19.4
  • Upgrade wasmd to v0.29.2
  • Upgrade pstake-native v1.3.1
  • Upgrade tendermint to v0.34.23

Full Change Log

Getting Prepared for the Upgrade

If using cosmovisor, manually build & copy the persistenceCore binary to . Please follow the upgrade guide

If not using cosmovisor, wait for your node to halt at the upgrade height, then install and run the v6.0.0 binary.

Note: Please use go version as part of v6 upgrade

Details of Upgrade Time

The proposal targets the upgrade proposal block to be 9601000, anticipated to be on 11th Jan 2023. Note that block times have high variance, so keep monitoring the time. See countdown here.

The upgrade is anticipated to take approx 30 minutes, during which time, there will not be any on-chain activity on the network.

In 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.

Proposal #12 overview

Total votes
1,297
Voters
1,284
Total deposit
512 XPRT