🟡 [ TESTNET ] Upcoming Software upgrade on test-core-2 chain to v11.15.0-rc0

Upgrade Height: 7,312,000
Proposal: https://www.mintscan.io/persistence-testnet/proposals/82/
Tag: https://github.com/persistenceOne/persistenceCore/releases/tag/v11.15.0-rc0

ETA to upgrade: ~18 hour 35 mins
Countdown: https://www.mintscan.io/persistence-testnet/block/7312000

Would request all our testnet validators to prepare for upgrade accordingly!
Thank you!

🟢 [MAINNET] Persistence Core-1 v11.15.0 Upgrade

🏗️ Would request everyone to vote and prepare accordingly!

Upgrade details:
Proposal: https://www.mintscan.io/persistence/proposals/116/
Height: 18,507,000
Release: https://github.com/persistenceOne/persistenceCore/releases/tag/v11.15.0

Timelines:
Upgrade time: Sept 19th 2024, (~11:40 AM UTC)
Countdown: https://www.mintscan.io/persistence/block/18507000

🟠 [ MAINNET ] Reminder for Persistence Core-1 v11.15.0 Upgrade

ETA: ~ 15 Hours 22 mins!

Note: Please acknowledge upgrade readiness by reacting with a checkmark to this message.

🟢 [ MAINNET ] Persistence Core-1 v11.16.0 Upgrade

🏗️ Would request everyone to prepare accordingly!

Upgrade details:
Proposal: https://www.mintscan.io/persistence/proposals/121/
Height: 19,611,500
Release: https://github.com/persistenceOne/persistenceCore/releases/tag/v11.16.0

Timelines:
Upgrade time: Dec 4th 2024, (~11:40 AM UTC)
Countdown: https://www.mintscan.io/persistence/block/19611500

🟠 [ MAINNET ] Reminder for Persistence Core-1 v11.16.0 Upgrade

ETA: ~ 1 Hours 12 mins!

Note: Please acknowledge upgrade readiness by reacting with a checkmark to this message.

🟢 [MAINNET] Persistence Core-1 v11.17.0 Upgrade

🏗️ Would request everyone to prepare accordingly!

Upgrade details:
Proposal: https://www.mintscan.io/persistence/proposals/126/
Height: 20,606,500
Release: https://github.com/persistenceOne/persistenceCore/releases/tag/v11.17.0

Timelines:
Upgrade time: Feb 10th 2025, (~12:13 AM UTC)
Countdown: https://www.mintscan.io/persistence/block/20606500

🟠 [MAINNET] Reminder for Persistence Core-1 v11.17.0 Upgrade

ETA: ~ 2 Hours 45 mins!

Note: Please acknowledge upgrade readiness by reacting with a checkmark to this message.

🔴 [MAINNET] Emergency Upgrade

Hello @Validators, we are planning to perform an emergency upgrade. Please reply with 👍 if you're available

🔴 UPDATE: [MAINNET] Emergency Upgrade


We'll be proceeding with the upgrade tomorrow as we need more time to resolve the errors and build the binary. Additionally, not all validators are currently available.
We'll update you on the exact timing, but it will take place in the afternoon/evening GST (Morning/noon UTC) time when most validators are available.

Thank you all for your prompt response!

🔴 [ MAINNET Validators ] Emergency Upgrade for core-1 chain to v11.18.0

IT IS CONSENSUS BREAKING, apply the fix only on height #20765700
Tag: v11.18.0
Release: https://github.com/persistenceOne/persistenceCore/releases/tag/v11.18.0
ETA: ~ 4 hours 20 mins
Countdown: https://www.mintscan.io/persistence/block/20765700

-------------------------
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 = 20765700

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 20765700

Option 3-> If running node normally or inside docker, restart to run node with
persistenceCore start --halt-height 20765700

➡️ STEP 2: AT BLOCK-HEIGHT 20765700, WHEN CHAIN HALTS
Once the chain reaches halt height (20765700), 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

Feel free to ping us if you need any help!

🟠 [Mainnet Validator] Reminder for Emergency Upgrade for core-1 chain to v11.18.0

ETA: ~ 1 Hour

Note: Please acknowledge upgrade readiness in this tracker

Upgrade complete ✅

🟡 [ TESTNET ] Rolling emergency upgrade for testnet for test-core-1 chain to v11.18.0-rc0


https://github.com/persistenceOne/persistenceCore/releases/tag/v11.18.0-rc0

Tag: v11.18.0-rc0

Would request everyone to perform the rolling upgrade and update your status with 👍 on this message

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.

🔴 [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!

🟠 [ @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

Hey guys, let's start the chain (i.e complete step 3)

🔴 [ @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!

🟠 [ 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