Sei v6.4 upgrade adds a new switch to disable IBC asset transfers in and out

ME News Report, April 18 (UTC+8), Sei official announced that the Sei v6.4 upgrade has added a protocol-level switch for "closing IBC asset transfers," which will be officially enabled through governance proposals in the future. Sei suggests that if users hold some IBC assets on Sei, they should bridge them out to the original chain as soon as possible before the proposal passes; otherwise, related Cosmos native assets will no longer be transferable to Sei, and users may face the risk of assets being unrecoverable. Currently, assets that need urgent handling include: USDCet (Wormhole Ethereum USDC), USDCop (Wormhole Optimism USDC), USDTbs, ATOM, WBTC. Sei states that this adjustment is part of the transition to upgrade the network to "EVM-only chain" as part of advancing SIP-3. (Source: MLion)
SEI2.96%
ATOM0.09%
W-1.45%
View Original
This page may contain third-party content, which is provided for information purposes only (not representations/warranties) and should not be considered as an endorsement of its views by Gate, nor as financial or professional advice. See Disclaimer for details.
  • Reward
  • 5
  • 2
  • Share
Comment
Add a comment
Add a comment
KiteStringQuant
· 11h ago
Will governance token holders vote in favor or against later?
Feels like it will pass, but the community will definitely argue about it.
View OriginalReply0
GateUser-a4680931
· 11h ago
The reminder was timely, but why not just freeze it directly instead of waiting for a proposal? Are there technical hurdles in implementation?
View OriginalReply0
OneMoreReorg
· 11h ago
v6.4 this switch design is quite aggressive, directly cut off the transfer at the protocol level, the Cosmos ecosystem interoperability was really betrayed by its own people this time.
View OriginalReply0
ApyDaydreamer
· 11h ago
What is the rhythm of Sei's self-built stablecoin? Otherwise, what's the point of IBC USDC?
View OriginalReply0
PixelatedDriedFish
· 11h ago
This "Unable to retrieve" warning is quite straightforward; it's rare for project teams to be so upfront about the unpleasant truth.
View OriginalReply0