Releases: Stride-Labs/stride
v24.0.0
Stride v24.0.0
v24.0.0 - 2024-08-29
Upgrade Info - Proposal 249
Stride Proposal #249 seeks to upgrade the chain to the v24.0.0 tag (Pavo Release) of the Stride codebase at block height 10,755,701 which is estimated to occur on September 4th, 2024, 15:00 UTC. Because of the uncertainty in block times, please keep track of the Stride chain for a precise estimate.
Upgrade Features
This code adds the following features:
- stTIA airdrop code
- batched (un)delegations
Getting Prepared for the Upgrade
As always, we recommend validators use 64GB of RAM. 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.
We highly recommend upgrading with Cosmovisor. To do this, please manually build & copy the strided binary to /cosmovisor/upgrades/v24/bin/.
Details of Upgrade Time
The proposal targets the upgrade proposal block to be 10,755,701 anticipated to be on September 4th 2024, 15:00 UTC. Because blocks can occur at irregular intervals, please keep an eye on the Stride chain for a precise upgrade time.
In case anything concerning happens at upgrade time, we will notify all validators immediately on the #cc-announcements channel.
v24.0.0 - 2024-08-29
On-Chain changes
- batching delegations and undelegations (#1263)
- removed autopilot support for metadata in receiver field and increased memo lengths (#1273)
- changed osmosis swap type URL (#1275)
- v24 Import Paths (#1278)
- bumped wasmd to v0.46 (#1274)
- Loosened outer redemption rate bounds (#1280)
- fixed map nondeterminism (#1281)
Off-Chain changes
Stride v23.0.1
Adds an additional non-state breaking airdrop query to v23.0.0
v23.0.0
Stride v23.0.0
v23.0.0 - 2024-07-20
Upgrade Info - Proposal 247
Stride Proposal #247 seeks to upgrade the chain to the v23.0.0 tag (Centaurus Release) of the Stride codebase at block height 10,077,001 which is estimated to occur on July 24 2024, 23:30 UTC. Because of the uncertainty in block times, please keep track of the Stride chain for a precise estimate.
Upgrade Features
This code adds the following features:
- stTIA airdrop code
- batched (un)delegations
Getting Prepared for the Upgrade
As always, we recommend validators use 64GB of RAM. 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.
We highly recommend upgrading with Cosmovisor. To do this, please manually build & copy the strided binary to /cosmovisor/upgrades/v23/bin/.
Details of Upgrade Time
The proposal targets the upgrade proposal block to be 10,077,001 anticipated to be on July 24th 2024, 23:30 UTC. Because blocks can occur at irregular intervals, please keep an eye on the Stride chain for a precise upgrade time.
In case anything concerning happens at upgrade time, we will notify all validators immediately on the #cc-announcements channel.
v23.0.0 - 2024-07-19
On-Chain changes
- added airdrop module (#1235)
- removed trade route dead code (#1189)
- added wasm light client (#1224), (#1231)
- consolidated cli txs in to same file (#1211)
- v23 upgrade handler (final) (#1243)
- close delegation channel tx (#1242)
- v23 Import Paths (#1246)
- version bumps (#1187), (#1228)
- Add Default Config Settings (#1245)
Off-Chain changes
v22.0.0
Stride v22.0.0
v22.0.0 - 2024-04-22
Upgrade Info - Proposal 237
Stride Proposal #237 seeks to upgrade the chain to the v22.0.0 tag (Cygus Release) of the Stride codebase at block height 8681868 which is estimated to occur on April 22 2024, 13:30 UTC. Because of the uncertainty in block times, please keep track of the Stride chain for a precise estimate.
Upgrade Features
This upgrade adds the following features:
- updated rebate to use native denom instead of reward denom (#1162)
Getting Prepared for the Upgrade
As always, we recommend validators use 64GB of RAM. 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.
We highly recommend upgrading with Cosmovisor. To do this, please manually build & copy the strided binary to /cosmovisor/upgrades/v21/bin/.
Details of Upgrade Time
The proposal targets the upgrade proposal block to be 8681868 anticipated to be on April 22st 2024, 13:30 UTC. Because blocks can occur at irregular intervals, please keep an eye on the Stride chain for a precise upgrade time.
In case anything concerning happens at upgrade time, we will notify all validators immediately on the #cc-announcements channel.
v22.0.0 - 2024-04-22
On-Chain changes
- added v22 upgrade handler (#1174)
- Fix validator weight check (#1176)
- added stToken burn to unregister host zone function (#1175)
- added ibc-hooks (#1173)
- added event for redeem stake (#1182)
- parameterize max messages per ICA tx on host zone (#1177)
- remove GetConnectionIdFromICAPort, use connection ID from host zone (#1179)
- v22 Import Paths (#1183)
- fixed ibc hooks store key (#1184)
Off-Chain changes
- v21 Changelog (#1168)
v21.0.0
Stride v21.0.0
v21.0.0 - 2024-04-01
Upgrade Info - Proposal XXX
Stride Proposal #XXX seeks to upgrade the chain to the v21.0.0 tag (Cygus Release) of the Stride codebase at block height 8370738 which is estimated to occur on April 1 2024, 13:40 UTC. Because of the uncertainty in block times, please keep track of the Stride chain for a precise estimate.
Upgrade Features
This upgrade adds the following features:
- updated rebate to use native denom instead of reward denom (#1162)
Getting Prepared for the Upgrade
As always, we recommend validators use 64GB of RAM. 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.
We highly recommend upgrading with Cosmovisor. To do this, please manually build & copy the strided binary to /cosmovisor/upgrades/v21/bin/.
Details of Upgrade Time
The proposal targets the upgrade proposal block to be 8370738 anticipated to be on April 1st 2024, 13:40 UTC. Because blocks can occur at irregular intervals, please keep an eye on the Stride chain for a precise upgrade time.
In case anything concerning happens at upgrade time, we will notify all validators immediately on the #cc-announcements channel.
v21.0.0 - 2024-04-01
On-Chain changes
v20.0.0
Stride v20.0.0
v20.0.0 - 2024-03-25
Upgrade Info - Proposal XXX
Stride Proposal #XXX seeks to upgrade the chain to the v20.0.0 tag (Crux Release) of the Stride codebase at block height 8,269,628 which is estimated to occur on March 25th 2024, 13:00 UTC. Because of the uncertainty in block times, please keep track of the Stride chain for a precise estimate.
Upgrade Features
This upgrade adds the following features:
- Upgraded ICS to 4.0
- Add community pool rebate feature
Getting Prepared for the Upgrade
As always, we recommend validators use 64GB of RAM. 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.
We highly recommend upgrading with Cosmovisor. To do this, please manually build & copy the strided binary to /cosmovisor/upgrades/v20/bin/.
Details of Upgrade Time
The proposal targets the upgrade proposal block to be 8,269,628, anticipated to be on March 25th 2024, 13:00 UTC. Because blocks can occur at irregular intervals, please keep an eye on the Stride chain for a precise upgrade time.
In case anything concerning happens at upgrade time, we will notify all validators immediately on the #cc-announcements channel.
v20.0.0 - 2024-03-25
On-Chain changes
- v20 upgrade handler scaffolding (#1148)
- Upgraded ICS to 4.0 (#1153,#1157)
- add community pool rebate feature (#1135)
- v20 Import Paths (#1155)
Off-Chain changes
v19.0.0
Stride v19.0.0
v19.0.0 - 2024-03-08
Upgrade Info - Proposal 233
Stride Proposal #233 seeks to upgrade the chain to the v19.0.0 tag (Pictor Release) of the Stride codebase at block height 8,064,608 which is estimated to occur on March 11th 2024, 11:00 UTC. Because of the uncertainty in block times, please keep track of the Stride chain for a precise estimate.
Upgrade Features
This upgrade adds the following features:
- Adds stDYM Code
- Add permissioned CosmWasm to support Hyperlane contracts
- File re-orgs
Getting Prepared for the Upgrade
As always, we recommend validators use 64GB of RAM. 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.
We highly recommend upgrading with Cosmovisor. To do this, please manually build & copy the strided binary to /cosmovisor/upgrades/v19/bin/.
Details of Upgrade Time
The proposal targets the upgrade proposal block to be 8,064,608, anticipated to be on March 11th 2024, 11:00 UTC. Because blocks can occur at irregular intervals, please keep an eye on the Stride chain for a precise upgrade time.
In case anything concerning happens at upgrade time, we will notify all validators immediately on the #cc-announcements channel.
v19.0.0 - 2024-03-07
On-Chain changes
- fixed vscode settings (#1111)
- stakeibc re-org part 1 (keepers) (#1112)
- Add cosmwasm (#1103)
- send staketia redemption rate to oracle (#1115)
- stakeibc file re-org part 2 (epochly functions) (#1113)
- stakeibc file re-org part 3 (ibc, ica, icq, and utilities) (#1116)
- stakeibc file re-org part 4 (grpc query) (#1117)
- stakeibc file re-org part 5 (msg_server) (#1120)
- set wasm permissions (#1125)
- switched to open sourced rate limit module (#1123)
- added sttia rate limit (#1127)
- Add x/stakedym (#1126)
Off-Chain changes
v18.0.0
Stride v18.0.0
v18.0.0 - 2024-01-27
Upgrade Info - Proposal 229
Stride Proposal #229 seeks to upgrade the chain to the v18.0.0 tag (Chamaeleon Release) of the Stride codebase at block height 7,464,647 which is estimated to occur on January 30th 2024, 11:00 UTC. Because of the uncertainty in block times, please keep track of the Stride chain for a precise estimate.
Upgrade Features
This upgrade adds the following features:
- Adds additional queries, e.g. querying redemption records for multiple addresses
- Reset delegation change in progress to 0 when a channel is restored
- V18 Upgrade Migrations
- Update RPC queries
Getting Prepared for the Upgrade
As always, we recommend validators use 64GB of RAM. 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.
We highly recommend upgrading with Cosmovisor. To do this, please manually build & copy the strided binary to /cosmovisor/upgrades/v18/bin/.
Details of Upgrade Time
The proposal targets the upgrade proposal block to be 7,464,647, anticipated to be on January 30th 2024, 11:00 UTC. Because blocks can occur at irregular intervals, please keep an eye on the Stride chain for a precise upgrade time.
In case anything concerning happens at upgrade time, we will notify all validators immediately on the #cc-announcements channel.
v18.0.0 - 2024-01-27
On-Chain changes
v17.0.0
Stride v17.0.0
v17.0.0 - 2024-01-12
Upgrade Info - Proposal 226
Stride Proposal #226 seeks to upgrade the chain to the v17.0.0 tag (Leo Release) of the Stride codebase at block height 7,244,427 which is estimated to occur on January 15th 2024, 12:00 UTC. Because of the uncertainty in block times, please keep track of the Stride chain for a precise estimate.
Upgrade Features
This upgrade adds the following features:
- Adds support for stDYDX, including autoinvesting real yield
- Autopilot v2 (liquid stake and forward, redeem)
- Refactor Unbonding Logic and Resume INJ unbondings
- Adds miscellaneous safety features (validator weight cap, disabling tokenization)
Getting Prepared for the Upgrade
As always, we recommend validators use 64GB of RAM. 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.
We highly recommend upgrading with Cosmovisor. To do this, please manually build & copy the strided binary to /cosmovisor/upgrades/v17/bin/.
Details of Upgrade Time
The proposal targets the upgrade proposal block to be 7,244,427, anticipated to be on January 15th 2024, 12:00 UTC. Because blocks can occur at irregular intervals, please keep an eye on the Stride chain for a precise upgrade time.
In case anything concerning happens at upgrade time, we will notify all validators immediately on the #cc-announcements channel.
v17.0.0 - 2024-01-12
On-Chain changes
- sDYDX: Phase 1/3 - LS & Redeem (#926)
- Properly Account for slash_query_in_progress in Unbondings (#981)
- Cleanup V14 (
DelegationChangesInProgress) (#1017) - Add claim rewards ICA (#961)
- sDYDX: Phase 2/3 - Auto-trade reward token revenue (#955)
- Cleanup v15 (#950)
- Removed zero error case in slash query (#1025)
- Sort unbonding prioritization by validator capacity (#1018)
- Add validator weight cap (#1032)
- Whitelisted all gov proposals (#1028)
- Allow multiple redemptions per epoch (#1009)
- Refresh autopilot LS + forward (#996)
- Add RedeemStake to autopilot (#1012)
- Upgraded to ics v3.2.0 (#1043)
- Autopilot hashed sender (#1038)
- Add pfm (#889)
- Autopilot fallback address (#1039)
- Add V17 upgrade handler (#1029)
- Dynamically update user redemption records during unbonding (#1053)
- V17 Import Paths (#1061)
- Disable tokenization on CosmosHub Delegation Account in Hooks (#1066)
- Update ICQ for compatibility with IBC v7.3.1 (#1068)
- Rename native amount and host zone unbonding status (#1071)
Off-Chain changes
- Add security instructions (#990)
- Bump go 1.19 -> 1.21 (#1052)
- Add PFM testing scripts (#1054)
- Fix bug in changelog script (#1060)
- Adjust testing scripts (#1064)
- Ignore host's check_go_version (#1072)
- upgrade integration tests for v17 (#1073)
🔨 Build from source
git clone https://github.com/Stride-Labs/stride
cd stride && git checkout v17.0.0
make build
v16.0.0
Stride v16.0.0
v16.0.0 - 2023-10-14
Upgrade Info - Proposal 220
Stride Proposal #220 seeks to upgrade the chain to the v16.0.0 tag (Bootes Release) of the Stride codebase at block height 5,932,395 which is estimated to occur on October 18th 2023, 12:00 UTC. Because of the uncertainty in block times, please keep track of the Stride chain for a precise estimate.
Upgrade Features
This upgrade adds the following features:
- Resumes the cosmoshub-4 host zone
Getting Prepared for the Upgrade
As always, we recommend validators use 64GB of RAM. 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.
We highly recommend upgrading with Cosmovisor. To do this, please manually build & copy the strided binary to /cosmovisor/upgrades/v16/bin/.
Details of Upgrade Time
The proposal targets the upgrade proposal block to be 5,932,395, anticipated to be on October 18th 2023, 12:00 UTC. Because blocks can occur at irregular intervals, please keep an eye on the Stride chain for a precise upgrade time.
In case anything concerning happens at upgrade time, we will notify all validators immediately on the #cc-announcements channel.
v16.0.0 - 2023-10-14
On-Chain changes
🔨 Build from source
git clone https://github.com/Stride-Labs/stride
cd stride && git checkout v16.0.0
make build