Skip to content

Releases: Stride-Labs/stride

v31.2.0

23 Jan 21:11
fec6f9e

Choose a tag to compare

v31 release with comet bumped to v0.38.21

v31.0.0

17 Dec 23:01
4114e6c

Choose a tag to compare

Stride v31.0.0

v31.0.0 - 2025-12-17

Upgrade Info

  1. Updates the Celestia unbonding time for staketia

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/v31/bin/.

Details of Upgrade Time

The proposal targets the upgrade proposal block to be 23455432 anticipated to be on Tuesday Oct 15th 2025 at 12 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.

v30.0.0

19 Nov 00:52
9817538

Choose a tag to compare

Stride v30.0.0 — Hydrus

v30.0.0 - 2025-11-18

Upgrade Info – Proposal XXX

Stride Proposal #XXX seeks to upgrade the chain to the v30.0.0 (Hydrus) tag of the Stride codebase at block height 25688652, which is estimated to occur on Tuesday Nov 25th 2025 at 14:15 UTC.

Because of the uncertainty in block times, please keep track of the Stride chain for a precise estimate.

Upgrade Features

  • Add cryptocrew to Stride's validator set.

This is a small upgrade focused on expanding the PoA validator set. No other functional changes are planned beyond the validator-set update.

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 and copy the strided binary to:

$DAEMON_HOME/cosmovisor/upgrades/v30/bin/

v29.1.1

14 Oct 19:08
ffd1fc2

Choose a tag to compare

Stride v29.1.1 is not consensus breaking.

v29.1.1 - 2025-10-14

  1. Bumped cometbft to v0.38.19 (#1465)

v29.0.0

10 Oct 19:59
2c4f781

Choose a tag to compare

Stride v29.0.0

v29.0.0 - 2025-10-15

Upgrade Info - Proposal 269

Stride Proposal #269 seeks to upgrade the chain to the v29.0.0 tag (Phoenix Release) of the Stride codebase at block height 23455432 which is estimated to occur on Wednesday Oct 15th 2025 at 12 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:

  1. ICS Migration - Opt-In PSS with PoA style set (#1456)
  2. added gov tx to deprecate host zones (#1457)
  3. Added burn tx (#1458)
  4. Versioning (#1462)

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/v29/bin/.

Details of Upgrade Time

The proposal targets the upgrade proposal block to be 23455432 anticipated to be on Tuesday Oct 15th 2025 at 12 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.

v29.0.0 - 2025-10-15

On-Chain changes

  1. ICS Migration - Opt-In PSS with PoA style set (#1456)
  2. added gov tx to deprecate host zones (#1457)
  3. Added burn tx (#1458)
  4. Versioning (#1462)

v28.0.0

05 Aug 16:52
098d302

Choose a tag to compare

Stride v28.0.0

v28.0.0 - 2025-08-05

Upgrade Info - Proposal 266

Stride Proposal #266 seeks to upgrade the chain to the v280.0 tag (Pyxis Release) of the Stride codebase at block height 21,199,112 which is estimated to occur on Tuesday August 12th 2025, 16: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:

  • Upgraded to Cosmos SDK v0.50
  • Disabled community pool liquid staking
  • Reduced max ICAs per batch for stBAND
  • Cleaned up ICQ queries and duplicate event emissions
  • Migrated integration tests to TypeScript; added tests for Autopilot and BBB systems
  • Action gov prop 262

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/v28/bin/.

Details of Upgrade Time

The proposal targets the upgrade proposal block to be 21,199,112 anticipated to be on Tuesday August 12th 2025, 16: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.

v28.0.0 - 2025-08-05

On-Chain changes

  1. Upgrade to sdk v0.50 (#1381)
  2. disable community pool liquid stake feature (#1423)
  3. v28 Upgrade Handler + Bounds Change (#1422)
  4. Delete Stale ICQ Query (#1425)
  5. Decrease max ICAs per batch (#1426)
  6. v28 Import Paths (#1428)
  7. removed duplicate event emissions in cache context wrapper (#1415)

Off-Chain changes

  1. [tests] Migrate core integration tests from bats to TypeScript framework (#1417)
  2. Autopilot and BBB integration tests (#1427)

v27.0.0

12 Jun 03:10
d4c9b59

Choose a tag to compare

Stride v27.0.0

v27.0.0 - 2025-06-11

Upgrade Info - Proposal 264

Stride Proposal #264 seeks to upgrade the chain to the v27.0.0 tag (Lacerta Release) of the Stride codebase at block height 19,488,491 which is estimated to occur on Tuesday June 17th 2025, 14: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:

  • Migrate LSM Liquid Staking to x/liquid
  • Minor technical upgrades
  • v27 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/v27/bin/.

Details of Upgrade Time

The proposal targets the upgrade proposal block to be 19,488,491 anticipated to be on Tuesday June 17th 2025, 14: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.

v27.0.0 - 2025-06-11

On-Chain changes

  1. add utils.SafeSendCoins() (#1373)
  2. standardize amino names (#1386)
  3. Unit Tests for stakeibc CLI (#1220)
  4. Migrated LSM Liquid stake to x/liquid (#1407)
  5. v27 upgrade handler (#1408)
  6. v27 import paths (#1409)
  7. Localstride fixes (#1410)
  8. Updated redemption rate bounds in v27 handler (#1414)

Off-Chain changes

  1. Fix auction query conflict (#1374)
  2. bump wasmvm (#1376)
  3. Bump tj-actions/changed-files from 41 to 46 in /.github/workflows (#1384)

v26.0.3

13 Mar 18:48
v26.0.3
32341bf

Choose a tag to compare

Stride v26.0.3 is not consensus breaking.

v26.0.3 - 2025-03-13

  1. CLI: Fix strided tx place-bid to support big numbers for [selling-token-amount] & [payment-token-amount]

v26.0.2

07 Mar 09:18
v26.0.2
b35abff

Choose a tag to compare

Stride v26.0.2 is not consensus breaking.

v26.0.2 - 2025-03-07

  1. REST: Fix auction queries paths (#1378)

v26.0.1

05 Mar 14:58
v26.0.1
71567c4

Choose a tag to compare

Stride v26.0.1 is not consensus breaking.

v26.0.1 - 2025-03-05

  1. REST: Fix auction query conflict (#1374)
  2. CLI: Fix strided tx auction create-auction to correctly parse minBidAmount (#1375)