Proposal Details
Proposal #42
Proposal title
PersistenceCore v8 Pacaya Upgrade
Submit time
Deposit end time
Voting start time
Voting end time
Tally result
Proposal #42 description
PersistenceCore v8 Pacaya Upgrade
This is a proposal to do a software upgrade to the
Pacaya is an active complex volcano in Guatemala known for its persistent activity.
Changelog
- Upgrades cosmos-sdk from to v0.47.3 with an LSM fork created by Persistence, including barberry security fix
- Migrates from tendermint to cometbft
- Upgrades ibc-go from to v7.2.0 LSM fork including huckleberry security fix
- Upgrades wasmd from to v0.40.2 LSM fork & wasmvm toincluding cherry bugfix
- Some SDK 47 things to keep in mind:
- The SDK version includes some key store migration for the CLI. Make sure you backup your private keys before doing upgrade! You can not switch back to v45 keys
- CLI: ,,,and others are now undercommand as parent
- CLI: was removed. You need to query the result for a TX withinstead
- Upgrades persistence-sdk from to v2.1.1
- Upgrades pstake-native from to v2.2.3
- Adds wasm-bindings for querying state
New Modules
- IBC hooks
- PFM (Packet Forwarding Middleware)
- Persistence - disabled for now, WIP
- Persistence - this deprecatesmodule
- Skip's POB for MEV auctions
MinCommissionRate
-
is set to 5%, which was proposed here
Note
During upgrade,
Validator'swill be set to, if it is lower than the(i.e. 5%),
and Validator'swill be set to(if lower than 10%) to give validator some margin to work with.
MinInitialDepositRatio
- is set to, which means a proposal cannot be submitted with deposit lower thanof
MinSelfDelegation
Due to LSM implementation, the
LSM Params
- is set to
- is set to
- is set to
About pStake v2.2.x
This is a major release for the pStake app, focused on enhancing the liquid staking capabilities of the platform and increase its future functionality and adaptability.
Other dependencies and upgrades
Checkout the release log v8.0.0 and release log v8.1.0 for what's changed.
How to upgrade
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 ask questions, report upgrade status, report technical issues, and to build social consensus should the need arise. If you don't have access, please reach out to someone from the Persistence team directly.