This post documents a Moderator SubDAO action to remove several Bitfrost variants from Osmosis alloyed assets.
The Moderator SubDAO continues to review all Alloys to assess the risk vs. benefit of the included variants. Alloys are intended to improve the user experience by combining equivalent bridged assets, but every additional bridge variant also adds operational and bridge risk.
This action is being taken because the bridge is expected to close down. No final shutdown date has been confirmed at this time, so this update is intended as an initial risk-reduction step for unused variants.
Adjustment Summary
The Moderator SubDAO will remove the following Interface variants from their relevant alloy sets:
- XRP.int3
- BTC.int3
- SOL.int3
- TON.int3
These variants are currently unused and do not provide sufficient benefit to justify their retention in the alloys while the bridge is expected to wind down.
DOGE.int3 will not be removed in this initial action. It will be removed at a later date as DOGE.int3 is phased out of the DOGE alloy and replaced with other DOGE variants.
Several other Alloyed Assets with minimal liquidity, such as ZEC, LTC, and BCH, are left in place as Bitfrost is the only available route and cannot have the sole variant removed.
Rationale
The Bitfrost bridge is expected to close, increasing the operational risk of keeping .Int3 variants within Osmosis alloys.
Key considerations:
- These variants are minimally used or unused within their relevant alloys.
- Each additional bridge variant adds operational and bridge risk.
- There is no confirmed end date, so the safest approach is to begin with unused variants rather than wait until a deadline is announced.
- Removing unused variants now reduces alloy complexity without affecting normal user activity.
Maintaining unused variants in the alloys would expose Osmosis to avoidable risk without a corresponding benefit.
Outcome
- XRP.int3, BTC.int3, SOL.int3 and TON.int3 are removed from their relevant alloys.
- The affected alloys remain functional through other routes while becoming simpler and lower risk.
- This post is provided for transparency around Moderator SubDAO action and is not a draft proposal.