Ronin migrates its legacy bridge to Chainlink CCIP

Ronin, the blockchain for gaming, has migrated its Ronin Bridge to Chainlink’s cross-chain interoperability protocol.

The Ronin Network (RON), whose web3 gaming platform was created by the Sky Mavis team behind Axie Infitnity (AXS) game, announced the completion of the migration to Chainlink’s (LINK) Cross-Chain Interoperability Protocol on April 25. 

CCIP is now the Ronin Bridge’s canonical cross-chain infrastructure provider. The milestone comes a few months after a validator community vote in October 2024 saw the platform pick Chainlink over LayerZero and Axelar.

As of the announcement, Chainlink is helping to secure over $450 million worth of assets on Ronin. 

Commenting on the development, Trung Nguyen, chief executive officer and co-founder of Sky Mavis, said:

“Migrating to Chainlink CCIP is a major unlock for Ronin as we scale into the most accessible and secure gaming and consumer chain in Web3. Developers get cross-chain infrastructure to build fast and secure, while users can easily bridge assets across the multi-chain ecosystem, opening the door to the next generation of games and apps.”

Ronin Bridge suffered a major exploit in 2022 with hackers stealing over $600 million worth of crypto. The platform paused transactions on the bridge in August 2024 amid suspicious $10 million withdrawal.

Adopting Chainlink CCIP is thus one of the efforts to increase the security of bridged assets. The platform also plans to tap into other Chainlink solutions to improve user experience and adoption, including gaining traction in decentralized finance.

With the migration, users can now transfer all supported tokens, includding AXS, YGG and BANANA as well as USDC and Wrapped Bitcoin to and from Ronin. The transfers will be via Chainlink CCIP-powered Ronin Bridge app.

Despite the latest move, the deprecated Ronin Bridge tab remains visible. According to the Ronin Network team, a number of users are yet to claim their tokens on Ethereum. These pending withdrawal requests are why the legacy bridge is still visible.