announcements
Jun 30, 2025
·
5 min read
Wormhole extends grace period for Terra Classic, Terra, Karura and Acala.
Previously, it was communicated that Wormhole would stop services on a number of chains this summer, including the ones mentioned above. On June 6th, Terra Classic (columbus-5), Karura, Acala, XPLA and Oasis have been disconnected from Wormhole. Originally, Terra (phoenix-1) was planned for disconnection on June 26th, alongside the Cosmos tab on portalbridge.com.
The Wormhole Guardians have decided to temporarily restore messaging on Terra Classic, Karura and Acala, and grant an extension for Terra and the Cosmos tab. Until the 14th July 2025 date, the following services will be available on portalbridge.com to allow more users to exit the affected chains:
After 14th July 2025, the following will no longer be possible:
After 14th July 2025, the following will still be possible, assuming a third party hosts a frontend and sets up IBC relaying (as described in the previous blog post):
After the 14th July 2025 date, the following will still be possible on portalbridge.com:
Additional notes:
The Guardian Network, which independently governs the security and sustainability of Wormhole’s cross-chain messaging infrastructure, has made the decision to adjust support for several blockchain networks on the Wormhole platform. This decision follows the comprehensive analysis of network metrics, including transaction volumes, resource utilization, and long-term sustainability factors.
The following chains will undergo network support changes:
Full Deprecation
Frontend Transition
Fully deprecating these networks involves the following 2 steps:
No delisting or messaging cutoff will occur before the summer of 2025.
Select Cosmos chains will transition from first-party frontend support and discontinue subsidized IBC relaying. This involves the following 2 steps:
No changes (Portal delisting or IBC relayer cutoff) will occur before the summer of 2025.
Note that:
The teams below have indicated that token transfers will continue to be available uninterrupted for these chain.
Given that Wormhole Gateway and the existing IBC channels will continue to operate as normal, anyone can set up their frontend solution to facilitate token transfers. To do so, there are 2 necessary steps:
The easiest way is to use a version of the Wormhole Connect frontend widget (0.x.x) that has support for these chains. Please find instructions to set these up in the repository’s readme at the indicated commit height. You’re also free to fork the repository and modify Wormhole Connect according to your needs.
Alternatively, if you’d like to build your own frontend, this is the SDK being used by Wormhole Connect 0.x.x: https://www.npmjs.com/package/@certusone/wormhole-sdk/v/0.10.18
If you don’t want to host your own IBC relaying infrastructure, we recommend getting in touch with one of the service providers to set them up for you. You’ll need the channel identifier between the Cosmos chain you want to set up IBC relaying for, and Wormhole Gateway (cosmos chain ID: wormchain)
The service provider the Wormhole Foundation recommends and used is CryptoCrew Validators: https://ccvalidators.com/
Wormhole is the leading interoperability platform that powers multichain applications and bridges at scale. Wormhole provides developers access to liquidity and users on over 30 of the leading blockchain networks, enabling use cases that span DeFi, NFTs, governance, and more.
The wider Wormhole network is trusted and used by teams like Circle and Uniswap. To date, the platform has facilitated the transfer of over 40 billion dollars through over 1 billion cross-chain messages. To learn more about Wormhole, follow on Twitter, join the Discord, or read more on the blog.