Persistence Validators Announcements
Hello [Mainnet Validators], we have received a security update from ICF and hence we are planning to perform an emergency upgrade tomorrow. More details to follow
[Mainnet Validators] We'll be upgrading today at block height - https://www.mintscan.io/persistence/block/20870000
(We'll have to halt the chain at this height like last upgrade)
Full details will be out shortly in next message.
(We'll have to halt the chain at this height like last upgrade)
Full details will be out shortly in next message.
Persistence Validators Announcements
Hello [Mainnet Validators], we have received a security update from ICF and hence we are planning to perform an emergency upgrade tomorrow. More details to follow
🔴 [MAINNET] Emergency Upgrade for core-1 chain to v11.19.0
IT IS CONSENSUS BREAKING, apply the fix only on height #20870000
Tag: v11.19.0
Release: https://github.com/persistenceOne/persistenceCore/releases/tag/v11.19.0
ETA: ~ 6 hours
Countdown: https://www.mintscan.io/persistence/block/20870000
-------------------------
GUIDE FOR VALIDATORS
➡️ STEP 1: SET CHAIN HALT HEIGHT
Option 1-> put halt height in config/app.toml
#HaltHeight contains a non-zero block height at which a node will gracefully
#halt and shutdown that can be used to assist upgrades and testing.
#Note: Commitment of state will be attempted on the corresponding block.
halt-height = 20870000
save and restart the node.
Option 2-> if running with cosmovisor, can restart node to run with --halt-height flag
cosmovisor run start --halt-height 20870000
Option 3-> If running node normally or inside docker, restart to run node with
persistenceCore start --halt-height 20870000
➡️ STEP 2: AT BLOCK-HEIGHT 20870000, WHEN CHAIN HALTS
Once the chain reaches halt height (20870000), the chain (i.e consensus) will stop (i.e it will stop producing blocks).
Stay in the STOPPED state till the team confirm 67% VP has reached (before restarting binary).
➡️ STEP 3: TEAM CONFIRMS THE HALT AND ASKS TO RESTART THE CHAIN
Once the team confirms, validator can now swap the persistenceCore binary to the NEW binary and restart the node.
NOTE: This time without the halt height flag and/or reset it from app.toml if it was set there. (i.e halt-height=0)
Commands for restarting the node: persistenceCore start or cosmovisor run start
Now, once we reach 67% consensus, the chain will start producing blocks again.
--
‼️ [Important] TRACKER
To track the progress, we have created this sheet where every validator can update their status.
https://docs.google.com/spreadsheets/d/12RvCH0Ar71QlogkUf8FsOgko3OIUZ1h5QJImx_Io4_M/edit?gid=668092882#gid=668092882
Feel free to ping us if you need any help!
IT IS CONSENSUS BREAKING, apply the fix only on height #20870000
Tag: v11.19.0
Release: https://github.com/persistenceOne/persistenceCore/releases/tag/v11.19.0
ETA: ~ 6 hours
Countdown: https://www.mintscan.io/persistence/block/20870000
-------------------------
GUIDE FOR VALIDATORS
➡️ STEP 1: SET CHAIN HALT HEIGHT
Option 1-> put halt height in config/app.toml
#HaltHeight contains a non-zero block height at which a node will gracefully
#halt and shutdown that can be used to assist upgrades and testing.
#Note: Commitment of state will be attempted on the corresponding block.
halt-height = 20870000
save and restart the node.
Option 2-> if running with cosmovisor, can restart node to run with --halt-height flag
cosmovisor run start --halt-height 20870000
Option 3-> If running node normally or inside docker, restart to run node with
persistenceCore start --halt-height 20870000
➡️ STEP 2: AT BLOCK-HEIGHT 20870000, WHEN CHAIN HALTS
Once the chain reaches halt height (20870000), the chain (i.e consensus) will stop (i.e it will stop producing blocks).
Stay in the STOPPED state till the team confirm 67% VP has reached (before restarting binary).
➡️ STEP 3: TEAM CONFIRMS THE HALT AND ASKS TO RESTART THE CHAIN
Once the team confirms, validator can now swap the persistenceCore binary to the NEW binary and restart the node.
NOTE: This time without the halt height flag and/or reset it from app.toml if it was set there. (i.e halt-height=0)
Commands for restarting the node: persistenceCore start or cosmovisor run start
Now, once we reach 67% consensus, the chain will start producing blocks again.
--
‼️ [Important] TRACKER
To track the progress, we have created this sheet where every validator can update their status.
https://docs.google.com/spreadsheets/d/12RvCH0Ar71QlogkUf8FsOgko3OIUZ1h5QJImx_Io4_M/edit?gid=668092882#gid=668092882
Feel free to ping us if you need any help!
👍3
Persistence Validators Announcements
🔴 [MAINNET] Emergency Upgrade for core-1 chain to v11.19.0 IT IS CONSENSUS BREAKING, apply the fix only on height #20870000 Tag: v11.19.0 Release: https://github.com/persistenceOne/persistenceCore/releases/tag/v11.19.0 ETA: ~ 6 hours Countdown: https://w…
🟠 [ @Validators ] Reminder for Emergency Upgrade for core-1 chain to v11.19.0
ETA: ~ 1 Hour 45 Mins
Comment: Both releases 11.19.0, and 11.19.1, have binary for 11.19.1 (which is built by the release process)
go-code/ binary/ blockchain code for both releases is the same, so building yourself any tag will be fine, we just tagged 11.19.1 because the release binary process failed for 11.19.0 (go version was updated to 1.23, but not updated in the CI..)
Note: Please acknowledge upgrade readiness in the tracker: https://docs.google.com/spreadsheets/d/12RvCH0Ar71QlogkUf8FsOgko3OIUZ1h5QJImx_Io4_M/edit?gid=668092882#gid=668092882
ETA: ~ 1 Hour 45 Mins
Comment: Both releases 11.19.0, and 11.19.1, have binary for 11.19.1 (which is built by the release process)
go-code/ binary/ blockchain code for both releases is the same, so building yourself any tag will be fine, we just tagged 11.19.1 because the release binary process failed for 11.19.0 (go version was updated to 1.23, but not updated in the CI..)
Note: Please acknowledge upgrade readiness in the tracker: https://docs.google.com/spreadsheets/d/12RvCH0Ar71QlogkUf8FsOgko3OIUZ1h5QJImx_Io4_M/edit?gid=668092882#gid=668092882
Persistence Validators Announcements
🟠 [ @Validators ] Reminder for Emergency Upgrade for core-1 chain to v11.19.0 ETA: ~ 1 Hour 45 Mins Comment: Both releases 11.19.0, and 11.19.1, have binary for 11.19.1 (which is built by the release process) go-code/ binary/ blockchain code for both releases…
Hey guys, let's start the chain (i.e complete step 3)
👍5
🔴 [ @Validators ] Emergency Upgrade for core-1 chain to v11.20.0
IT IS CONSENSUS BREAKING, apply the fix only on height #21060800
Tag: v11.20.0
Release: https://github.com/persistenceOne/persistenceCore/releases/tag/v11.20.0
ETA: ~ 14 hours 20 mins
Countdown: https://www.mintscan.io/persistence/block/21060800
-------------------------
GUIDE FOR VALIDATORS
➡️ STEP 1: SET CHAIN HALT HEIGHT
Option 1-> put halt height in config/app.toml
#HaltHeight contains a non-zero block height at which a node will gracefully
#halt and shutdown that can be used to assist upgrades and testing.
#Note: Commitment of state will be attempted on the corresponding block.
halt-height = 21060800
save and restart the node.
Option 2-> if running with cosmovisor, can restart node to run with --halt-height flag
cosmovisor run start --halt-height 21060800
Option 3-> If running node normally or inside docker, restart to run node with
persistenceCore start --halt-height 21060800
➡️ STEP 2: AT BLOCK-HEIGHT 21060800, WHEN CHAIN HALTS
Once the chain reaches halt height (21060800), the chain (i.e consensus) will stop (i.e it will stop producing blocks).
Stay in the STOPPED state till the team confirm 67% VP has reached (before restarting binary).
➡️ STEP 3: TEAM CONFIRMS THE HALT AND ASKS TO RESTART THE CHAIN
Once the team confirms, validator can now swap the persistenceCore binary to the NEW binary and restart the node.
NOTE: This time without the halt height flag and/or reset it from app.toml if it was set there. (i.e halt-height=0)
Commands for restarting the node: persistenceCore start or cosmovisor run start
Now, once we reach 67% consensus, the chain will start producing blocks again.
--
‼️ [Important] TRACKER
To track the progress, we have created this sheet where every validator can update their status.
https://docs.google.com/spreadsheets/d/12RvCH0Ar71QlogkUf8FsOgko3OIUZ1h5QJImx_Io4_M/edit?gid=1661183229#gid=1661183229
Feel free to ping us if you need any help!
IT IS CONSENSUS BREAKING, apply the fix only on height #21060800
Tag: v11.20.0
Release: https://github.com/persistenceOne/persistenceCore/releases/tag/v11.20.0
ETA: ~ 14 hours 20 mins
Countdown: https://www.mintscan.io/persistence/block/21060800
-------------------------
GUIDE FOR VALIDATORS
➡️ STEP 1: SET CHAIN HALT HEIGHT
Option 1-> put halt height in config/app.toml
#HaltHeight contains a non-zero block height at which a node will gracefully
#halt and shutdown that can be used to assist upgrades and testing.
#Note: Commitment of state will be attempted on the corresponding block.
halt-height = 21060800
save and restart the node.
Option 2-> if running with cosmovisor, can restart node to run with --halt-height flag
cosmovisor run start --halt-height 21060800
Option 3-> If running node normally or inside docker, restart to run node with
persistenceCore start --halt-height 21060800
➡️ STEP 2: AT BLOCK-HEIGHT 21060800, WHEN CHAIN HALTS
Once the chain reaches halt height (21060800), the chain (i.e consensus) will stop (i.e it will stop producing blocks).
Stay in the STOPPED state till the team confirm 67% VP has reached (before restarting binary).
➡️ STEP 3: TEAM CONFIRMS THE HALT AND ASKS TO RESTART THE CHAIN
Once the team confirms, validator can now swap the persistenceCore binary to the NEW binary and restart the node.
NOTE: This time without the halt height flag and/or reset it from app.toml if it was set there. (i.e halt-height=0)
Commands for restarting the node: persistenceCore start or cosmovisor run start
Now, once we reach 67% consensus, the chain will start producing blocks again.
--
‼️ [Important] TRACKER
To track the progress, we have created this sheet where every validator can update their status.
https://docs.google.com/spreadsheets/d/12RvCH0Ar71QlogkUf8FsOgko3OIUZ1h5QJImx_Io4_M/edit?gid=1661183229#gid=1661183229
Feel free to ping us if you need any help!
👍5
Persistence Validators Announcements
🔴 [ @Validators ] Emergency Upgrade for core-1 chain to v11.20.0 IT IS CONSENSUS BREAKING, apply the fix only on height #21060800 Tag: v11.20.0 Release: https://github.com/persistenceOne/persistenceCore/releases/tag/v11.20.0 ETA: ~ 14 hours 20 mins Countdown:…
🟠 [ Mainnnet ] Reminder for Emergency Upgrade for core-1 chain to v11.20.0
ETA: ~ 2 Hour 10 Mins
Note: Please acknowledge upgrade readiness in the tracker: https://docs.google.com/spreadsheets/d/12RvCH0Ar71QlogkUf8FsOgko3OIUZ1h5QJImx_Io4_M/edit?gid=1661183229#gid=1661183229
ETA: ~ 2 Hour 10 Mins
Note: Please acknowledge upgrade readiness in the tracker: https://docs.google.com/spreadsheets/d/12RvCH0Ar71QlogkUf8FsOgko3OIUZ1h5QJImx_Io4_M/edit?gid=1661183229#gid=1661183229
🟡 [TESTNET] Upcoming Software upgrade on test-core-2 chain to v11.21.0-rc0
Upgrade Height: 11,471,000
Proposal: https://www.mintscan.io/persistence-testnet/proposals/86
Tag: https://github.com/persistenceOne/persistenceCore/releases/tag/v11.21.0-rc0
ETA to upgrade: ~6 hours 55 mins
Countdown: https://www.mintscan.io/persistence-testnet/block/11471000
Would request all our testnet validators to prepare for upgrade accordingly!
Thank you!
Important Note: Would request all validators to make your own binaries as wasm vm version is updated since last testnet upgrade. Cosmovisor will work but before that add proper wasmvm version in
Upgrade Height: 11,471,000
Proposal: https://www.mintscan.io/persistence-testnet/proposals/86
Tag: https://github.com/persistenceOne/persistenceCore/releases/tag/v11.21.0-rc0
ETA to upgrade: ~6 hours 55 mins
Countdown: https://www.mintscan.io/persistence-testnet/block/11471000
Would request all our testnet validators to prepare for upgrade accordingly!
Thank you!
👍1
Persistence Validators Announcements
🟡 [TESTNET] Upcoming Software upgrade on test-core-2 chain to v11.21.0-rc0 Important Note: Would request all validators to make your own binaries as wasm vm version is updated since last testnet upgrade. Cosmovisor will work but before that add proper wasmvm…
🟠 [ TESTNET ] Reminder for Persistence Core-1 v11.21.0-rc0 Upgrade
ETA: ~ 24 mins!
ETA: ~ 24 mins!
👍2
🟢 [MAINNET] PersistenceCore v11.21.0 Upgrade
🏗️ Would request everyone to vote and prepare accordingly!
Upgrade details:
Proposal: https://www.mintscan.io/persistence/proposals/137/
Height: 22,492,000
Release: https://github.com/persistenceOne/persistenceCore/releases/tag/v11.21.0
Timelines:
Upgrade time: Jun 19th 2025 (±12:04 UTC)
Countdown: https://www.mintscan.io/persistence/block/22492000
🏗️ Would request everyone to vote and prepare accordingly!
Upgrade details:
Proposal: https://www.mintscan.io/persistence/proposals/137/
Height: 22,492,000
Release: https://github.com/persistenceOne/persistenceCore/releases/tag/v11.21.0
Timelines:
Upgrade time: Jun 19th 2025 (±12:04 UTC)
Countdown: https://www.mintscan.io/persistence/block/22492000
👍5
Persistence Validators Announcements
🟢 [MAINNET] PersistenceCore v11.21.0 Upgrade 🏗️ Would request everyone to vote and prepare accordingly! Upgrade details: Proposal: https://www.mintscan.io/persistence/proposals/137/ Height: 22,492,000 Release: https://github.com/persistenceOne/persiste…
🟠 [ MAINNET ] Reminder for v11.21.0 Upgrade
ETA: ~ 3 hours 25 mins
ETA: ~ 3 hours 25 mins
🔥3👍1
🟡 [ TESTNET ] Upcoming Software upgrade on test-core-2 chain to v12.0.0-rc0
Upgrade Height: 11903000
Proposal: https://www.mintscan.io/persistence-testnet/proposals/87
Tag: https://github.com/persistenceOne/persistenceCore/releases/tag/v12.0.0-rc0
ETA to upgrade: ~9 hours 15 mins
Countdown: https://www.mintscan.io/persistence-testnet/block/11903000
Would request all our testnet validators to prepare for upgrade accordingly!
Thank you!
Upgrade Height: 11903000
Proposal: https://www.mintscan.io/persistence-testnet/proposals/87
Tag: https://github.com/persistenceOne/persistenceCore/releases/tag/v12.0.0-rc0
ETA to upgrade: ~9 hours 15 mins
Countdown: https://www.mintscan.io/persistence-testnet/block/11903000
Would request all our testnet validators to prepare for upgrade accordingly!
Thank you!
🫡3🔥1
🟢 [MAINNET] PersistenceCore v12.0.0 Upgrade
🏗️ Would request everyone to vote and prepare accordingly!
Upgrade details:
Proposal: https://www.mintscan.io/persistence/proposals/141
Height: 22,892,000
Release: https://github.com/persistenceOne/persistenceCore/releases/tag/v12.0.0
Timelines:
Upgrade time: Jul 16th 2025 (±12:22 UTC)
Countdown: https://www.mintscan.io/persistence/block/22892000
🚨 NOTE: The block height mentioned in the proposal text is incorrect, the correct height is 22892000.
🏗️ Would request everyone to vote and prepare accordingly!
Upgrade details:
Proposal: https://www.mintscan.io/persistence/proposals/141
Height: 22,892,000
Release: https://github.com/persistenceOne/persistenceCore/releases/tag/v12.0.0
Timelines:
Upgrade time: Jul 16th 2025 (±12:22 UTC)
Countdown: https://www.mintscan.io/persistence/block/22892000
Please open Telegram to view this post
VIEW IN TELEGRAM
Persistence Validators Announcements
🟢 [MAINNET] PersistenceCore v12.0.0 Upgrade 🚨 NOTE: The block height mentioned in the proposal text is incorrect, the correct height is 22892000. 🏗️ Would request everyone to vote and prepare accordingly! Upgrade details: Proposal: https://www.mintsca…
🟠 [MAINNET] Reminder for v12.0.0 Upgrade
ETA: ~ 2 hours 47 mins
🚨 Note: Make sure the height is 22,892,000
ETA: ~ 2 hours 47 mins
Please open Telegram to view this post
VIEW IN TELEGRAM
👍2
🟡 [TESTNET] Upcoming Software upgrade on test-core-2 chain to v13.0.0-rc0
Upgrade Height: 12,671,000
Proposal: https://www.mintscan.io/persistence-testnet/proposals/88
Tag: https://github.com/persistenceOne/persistenceCore/releases/tag/v13.0.0-rc0
ETA to upgrade: ~21 hours 12 mins
Countdown: https://www.mintscan.io/persistence-testnet/block/12671000
Would request all our testnet validators to prepare for upgrade accordingly!
Thank you!
Upgrade Height: 12,671,000
Proposal: https://www.mintscan.io/persistence-testnet/proposals/88
Tag: https://github.com/persistenceOne/persistenceCore/releases/tag/v13.0.0-rc0
ETA to upgrade: ~21 hours 12 mins
Countdown: https://www.mintscan.io/persistence-testnet/block/12671000
Would request all our testnet validators to prepare for upgrade accordingly!
Thank you!
Persistence Validators Announcements
🟡 [TESTNET] Upcoming Software upgrade on test-core-2 chain to v13.0.0-rc0 Upgrade Height: 12,671,000 Proposal: https://www.mintscan.io/persistence-testnet/proposals/88 Tag: https://github.com/persistenceOne/persistenceCore/releases/tag/v13.0.0-rc0 ETA to…
🟠 [TESTNET] Reminder for Persistence Core-1 v13.0.0-rc0 Upgrade
ETA: ~ 4 hours 45 mins
ETA: ~ 4 hours 45 mins
🟡[ TESTNET ] Update on recent upgrade
We have fixed the issues faced during the upgrade. Please perform a rolling upgrade for your validator at the earliest convenience using the tag below:
https://github.com/persistenceOne/persistenceCore/releases/tag/v13.0.0-rc2
Thank you!
We have fixed the issues faced during the upgrade. Please perform a rolling upgrade for your validator at the earliest convenience using the tag below:
https://github.com/persistenceOne/persistenceCore/releases/tag/v13.0.0-rc2
Thank you!
GitHub
Release v13.0.0-rc2 · persistenceOne/persistenceCore
What's Changed
fix: update mod iavl pruning errors by @puneet2019 in #404
fix: cons addr prefix in staking keeper. by @puneet2019 in #406
Full Changelog: v13.0.0-rc1...v13.0.0-rc2
fix: update mod iavl pruning errors by @puneet2019 in #404
fix: cons addr prefix in staking keeper. by @puneet2019 in #406
Full Changelog: v13.0.0-rc1...v13.0.0-rc2
🫡2
🟢 [MAINNET] PersistenceCore v13.0.0 Upgrade
Upgrade details:
Proposal: https://www.mintscan.io/persistence/proposals/145/
Height: 23,794,500
Release: https://github.com/persistenceOne/persistenceCore/releases/tag/v13.0.0
Timelines:
Upgrade time: Sep 15th 2025, 11:40 AM (UTC)
Countdown: https://www.mintscan.io/persistence/block/23794500
Upgrade details:
Proposal: https://www.mintscan.io/persistence/proposals/145/
Height: 23,794,500
Release: https://github.com/persistenceOne/persistenceCore/releases/tag/v13.0.0
Timelines:
Upgrade time: Sep 15th 2025, 11:40 AM (UTC)
Countdown: https://www.mintscan.io/persistence/block/23794500
👍5
Persistence Validators Announcements
🟢 [MAINNET] PersistenceCore v13.0.0 Upgrade Upgrade details: Proposal: https://www.mintscan.io/persistence/proposals/145/ Height: 23,794,500 Release: https://github.com/persistenceOne/persistenceCore/releases/tag/v13.0.0 Timelines: Upgrade time: Sep…
🟠 [MAINNET] Reminder for v13.0.0 Upgrade
ETA: ~ 4 hours 43 mins
Note: Please acknowledge upgrade readiness by reacting with a checkmark to this message.
ETA: ~ 4 hours 43 mins
Note: Please acknowledge upgrade readiness by reacting with a checkmark to this message.
👍6
🟡 [ TESTNET ] Upcoming Software upgrade on test-core-2 chain to v14.0.0-rc0
Upgrade Height: 13,212,000
Proposal: https://www.mintscan.io/persistence-testnet/proposals/89
Tag: https://github.com/persistenceOne/persistenceCore/releases/tag/v14.0.0-rc0
ETA to upgrade: ~16 hours 24 mins
Countdown: https://www.mintscan.io/persistence-testnet/block/13212000
Would request all our testnet validators to prepare for upgrade accordingly!
Thank you!
Upgrade Height: 13,212,000
Proposal: https://www.mintscan.io/persistence-testnet/proposals/89
Tag: https://github.com/persistenceOne/persistenceCore/releases/tag/v14.0.0-rc0
ETA to upgrade: ~16 hours 24 mins
Countdown: https://www.mintscan.io/persistence-testnet/block/13212000
Would request all our testnet validators to prepare for upgrade accordingly!
Thank you!
👍1
Persistence Validators Announcements
🟡 [ TESTNET ] Upcoming Software upgrade on test-core-2 chain to v14.0.0-rc0 Upgrade Height: 13,212,000 Proposal: https://www.mintscan.io/persistence-testnet/proposals/89 Tag: https://github.com/persistenceOne/persistenceCore/releases/tag/v14.0.0-rc0 ETA…
🟠 [ TESTNET ] Reminder for Persistence test-core-2 v14.0.0-rc0 Upgrade
ETA: ~ 4 hours 18 mins
ETA: ~ 4 hours 18 mins