After launching the migration of its Ronin Bridge to Chainlink’s Cross-Chain Interoperability Protocol (CCIP), the Ronin Network has initiated a major upgrade with its move to its cross-chain infrastructure. The goal of this transition is to bring a safer and less susceptible bridging experience to users who transfer assets on Ethereum to Ronin.
All About Ronin Bridge & Chainlink CCIP Collaboration
Last year, Ronin Validators voted to adopt CCIP as the network’s canonical bridge protocol, which is a significant move following this. After making the migration process, now the world is migrating to Ronin and getting prepared to retire the legacy bridge and fully transition to Chainlink’s CCIP by the end of April. This upgrade will enable users to bridge a larger spectrum of tokens, including WETH, USDC, PIXEL, and AXS. Unfortunately, at this stage, some of those tokens, such as WBTC, LUA and LUAUSD, are not yet supported by the CCIP bridge. “The Ronin Bridge CCIP migration has begun! Stronger bridge security powered by Chainlink,” the Ronin team wrote on X. The announcement also highlighted the ability to “bridge WETH, USDC, PIXEL, AXS and more.” Moreover, it added that the older Ronin Bridge will be officially deprecated on April 21st. For further context, after the migration period, there will be two active bridges working concurrently: legacy Ronin Bridge and CCIP. From April 21, the older bridge will be shut down and from April 25 the CCIP bridge will take over all the cross chain functions. Moreover, Ronin Network said that all tokens still sitting on the legacy bridge will be automatically moved to CCIP by April 24 and 25. Last month, Ronin officially went live on OpenSea, expanding its reach beyond being the exclusive platform for collectibles like Axie Infinity. The blockchain network now enables users to trade and mint NFTs directly on the world’s largest NFT marketplace, as mentioned in our previous report.
Call To Action For Developers & Exchanges
Further, the key phrase in the article puts the ball in the court of developers and exchanges to act quickly and integrate CCIP into their systems. “We encourage you to grant dual minter rights to CCIP if you haven’t already,” the network advised. Being eminently clear that this migration is meant to secure the bar for cross-chain activity on Ronin, the entire team stated. The network sees CCIP as laying the groundwork for adoption and interaction within Web3 ecosystems, as it supports interoperability across more than 46 networks. “This alliance reinforces the connective tissue between our movement and other communities, bringing builders closer to countless Web3 users,” the Ronin team wrote in their announcement. Currently, users have to take no action as the transition progresses. However, from April 21 onwards, all bridge activity must be conducted through CCIP, the end of the CCIP legacy OD. Hence, this step brings Ronin one step closer to a full infrastructure shift to a more secure and scalable future of cross chain.
Recommended for you: