Transfer Stride Wind-Down Transmuter Pools to Osmosis Governance

This proposal has the Osmosis governance module accept admin rights over the 31 transmuter pools created for the Stride wind-down.

Background

Stride proposed an orderly wind-down of its chain in September 2026. Redemptions on Stride paused on 12 October while the backing assets unbonded, and the chain stopped producing blocks on 13 November at height 42,866,824.

Before the halt, Stride created 31 transmuter pools on Osmosis (code 996, transmuter 3.2.0) and funded each with the underlying native asset. Holders redeem by swapping their stToken for the native asset in the matching pool, at Stride’s final redemption rate. Each native asset is marked as corrupted in its pool, so the pools only swap one way: stTokens in, native assets out.

The pools cover the canonical stToken for each asset, plus variants that reached Osmosis through an intermediate chain (for example stATOM sent through Neutron), which are separate IBC denoms on Osmosis.

Admin rights

Each transmuter has an admin role, separate from the moderator. The admin can add assets, rescale normalisation factors, register and update limiters, set the alloyed denom’s metadata, assign the moderator, and transfer the admin role itself.

Today the admin of every pool is the Stride vault multisig, osmo1k8c2m5cn322akk5wy8lpt87dd2f4yh9afcd7af. With the Stride chain stopped, these pools are now long-lived Osmosis infrastructure, and their configuration should be controlled by Osmosis governance rather than by a team that is winding down.

The transmuter transfers admin rights in two steps: the current admin nominates a candidate, and the candidate accepts. On 13 November the Stride vault nominated the governance module (osmo10d07y265gmmuvt4z0w9aw880jnsr700jjeq4qp) as admin candidate on all 31 pools, in transactions B42053C3… and 369387E0….

Proposed change

This proposal executes claim_admin on each of the 31 pools from the governance module. Once it executes, the governance module is the admin of every pool, and further changes to them require a governance proposal.

Pool stToken Route to Osmosis
3628 stTIA Direct from Stride
3629 stTIA Via Cosmos Hub
3630 stTIA Via Neutron
3631 stTIA Via Agoric
3632 stTIA Via Celestia
3633 stTIA Via Dymension
3634 stATOM Direct from Stride
3635 stATOM Via Cosmos Hub
3636 stATOM Via Terra
3637 stATOM Via Neutron
3638 stATOM Via Agoric
3654 stATOM Via Secret
3695 stATOM Via Injective
3639 stDYDX Direct from Stride
3640 stDYDX Via Cosmos Hub
3641 stISLM Direct from Stride
3655 stISLM Via Haqq
3642 stINJ Direct from Stride
3643 stINJ Via Cosmos Hub
3656 stINJ Via Secret
3696 stINJ Via Injective
3644 stJUNO Direct from Stride
3645 stBAND Direct from Stride
3646 stBAND Via Cosmos Hub
3647 stOSMO Direct from Stride
3648 stOSMO Via Cosmos Hub
3649 stOSMO Via Secret
3650 stLUNA Direct from Stride
3651 stLUNA Via Terra
3652 stSOMM Direct from Stride
3653 stSAGA Direct from Stride

The moderator of every pool is unchanged. The proposal involves no contract migration or code change, and it doesn’t change any pool’s assets, rates, limiters or fees.

Benefits

  • Configuration of the redemption pools sits with Osmosis governance.
  • If a pool needs maintenance later, such as updating denom metadata or adjusting an asset after the backing is exhausted, governance can do it directly without depending on a multisig whose signers may no longer be active.

Concerns

  • This proposal transfers the admin role only. The native assets backing redemptions were deposited by the Stride vault, which holds the pool shares. Those shares, and the ability to withdraw the remaining backing, stay with the vault. The admin role can’t move another account’s shares.
  • Until this proposal executes, the Stride vault can still cancel or replace the nomination. If it did, the matching message, and the whole proposal, would fail at execution.

References

Target Onchain Date: 19th November 2026

This seems sensible now that Stride has stopped. One question from the holder side: will these redemption pools stay open with no deadline? Some people holding stATOM or stTIA probably don’t follow governance and may only notice months from now. It would also help if the app pointed them to the right pool, since a token that arrived through the Hub or Neutron is a different version from one that came directly from Stride.

Yes, they are intended to remain open indefinitely.

The routing on the app handles everything - each of the assets can be deposited directly from the chain it is on rather than having to route back through the, now shutdown, Stride chain. On the backend, there is a separate pool for each previously multi-hopped token.

1 Like