Stride v26.0.0
v26.0.0 - 2025-02-28
Upgrade Info - Proposal 261
Stride Proposal #261 seeks to upgrade the chain to the v26.0.0 tag (Fornax Release) of the Stride codebase at block height 16333361 which is estimated to occur on Tuesday Feb March 4th, 2025 at 18: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:
- Buyback and burn STRD with protocol revenue
- Auction and icqoracle modules
- Version bumps
- v26 upgrade paths and migration
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/v26/bin/.
Details of Upgrade Time
The proposal targets the upgrade proposal block to be 16333361 anticipated to be on Tuesday Feb March 4th, 2025 at 18: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.
v26.0.0 - 2025-02-28
On-Chain changes
- Buyback and Burn (#1318)
- fixed gosec errors (#1350)
- version bumps (ibc, pfm, wasmvm, cobra) (#1360, #1361, #1345)
- v26 Import Paths (#1367)
- Localstride changes (#1370)
- add txBytes support to
strided tx decodein addition to signBytes (#1347)