Proposal Details
Proposal #3
Proposal title
Upgrade PersistenceCore chain to v2
Submit time
Deposit end time
Voting start time
Voting end time
Tally result
Proposal #3 description
This on-chain upgrade proposal is for upgrading up Cosmos SDK version from v0.42.4 to v0.44.6 It includes few new modules like authz and feegrant.
- By voting YES to this proposal, you approve of adding these updates to PersistenceCore.
- By voting NO to this proposal, you do not approve of this upgrade.
Background
Since the last version of Cosmos SDK there have been a number of updates, fixes and new modules added to the Cosmos SDK, IBC and Tendermint. The following updates are included in persistenceCore v0.2.2:
- Bump PersistenceCore to 0.2.2 which notably includes fixes for the vesting accounts and two new modules outlined below. For a detailed difference between PersistenceCore v0.1.3 and v0.2.2 check diff.
- Add the authz module to the Cosmos Hub. `x/authz` is an implementation of a Cosmos SDK module, per ADR 30, that allows granting arbitrary privileges from one account (the granter) to another account (the grantee). Authorizations must be granted for a particular Msg service method one by one using an implementation of the `Authorization` interface.
- Add the feegrant module to the PersistenceCore mainnet. This module allows accounts to grant fee allowances and to use fees from their accounts. Grantees can execute any transaction without the need to maintain sufficient fees.
- Add IBC as a standalone module from the Cosmos SDK using version v2.0.2. See the CHANGELOG.md for details.
- Bumped Tendermint version to v0.34.14. For more details check CHANGELOG.md
Ready for Production
The release candidate for this update was run as a local testnet and a public testnet with a successful upgrade.
On Chain Upgrade Process
When the network reaches the halt height, the state machine program of the PersistenceCore mainnet will be halted. The classic method for upgrading requires all validators and node operators to manually substitute the existing state machine binary with the new binary. Because it is an onchain upgrade process, the blockchain will be continued with all the accumulated history with continuous block height.