Proposal Details
Proposal #7
Proposal title
PersistenceCore v3 Upgrade
Submit time
Deposit end time
Voting start time
Voting end time
Tally result
Proposal #7 description
PersistenceCore v3 Upgrade
This is a proposal to do a software upgrade to the v3.1.1 software tag of the persistenceCore codebase on block height 7791906, which is estimated to occur on Thursday Septermber 8th, UTC 16:00. Block times have high variance, so please monitor the chain for more precise time estimates.
Upgrade Features
This upgrade adds the following features:
Default coin type change from 750 to 118
We change the default coin type for the app chain to 118, similar to cosmos-hub, osmosis and other chains.
Add WASM module
Making the chain wasm compatible via governance. All wasm contracts can be uploaded via gov proposals, contract instantiation is also needs to go though gov proposals. Initially we have very strict permissions for wasm contracts.
Getting Prepared for the Upgrade
Follow detailed guide. In this upgrade, need to be careful about the creation of due to a bug in v2 persistenceCore. More details here. As 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. If using cosmovisor, manually build & copy the persistenceCore binary to /cosmovisor/upgrades/v3/bin/. If not using cosmovisor, wait for your node to halt at the upgrade height, then install and run the v3.1.1 binary.
Details of Upgrade Time
The proposal targets the upgrade proposal block to be 7791906, anticipated to be on Thursday September 8th, UTC 16:00. This uses an average block time of 6.2 seconds per block, derived from the Mintscan block explorer. 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.