Re Protocol Drops LayerZero for Chainlink CCIP as Exclusive Cross-Chain Bridge for reUSD

TLDR:

• Re Protocol migrates from LayerZero to Chainlink CCIP after an internal cross-chain security evaluation. 
• reUSD, with a $160M+ market cap, will use CCIP exclusively for secure multi-chain token distribution. 
• Each CCIP bridge lane is secured by 16 independent node operators, adding redundant transaction validation. 
• CCIP’s SOC 2 Type 2 attestation gives reUSD transfers institutional-grade security across all supported chains.

---

Re Protocol is transitioning from LayerZero to Chainlink CCIP for cross-chain infrastructure. The onchain reinsurance protocol, managing over $475 million in total value locked, made the switch after an internal security evaluation.

reUSD, its depository token with a market cap exceeding $160 million, will now rely solely on CCIP for multi-chain distribution. The decision reflects Re’s priority of security over speed when selecting technology partners.

Re Protocol Evaluates Cross-Chain Infrastructure Options

Re conducted an internal review of available bridging solutions before settling on Chainlink CCIP. The protocol weighed factors including track record, audit history, security model, and transparent operations. Speed of integration was not a deciding factor in this process.

The evaluation focused on infrastructure suitable for an asset backed by real-world risk capital. reUSD represents capital supporting a licensed reinsurer, so the bridging partner had to meet a genuinely high security standard. Re indicated it prefers to move deliberately rather than rebuild infrastructure later.

Cliff White, VP of Engineering at Re, spoke directly to the long-standing relationship with Chainlink. “Chainlink has been a foundational technology provider powering Re from the beginning,” White said. “It is an obvious choice to upgrade to Chainlink and secure the expansion of reUSD across chains.”

Chainlink CCIP secured the mandate by offering several built-in security features. Each CCIP bridge lane is validated by 16 independent, security-reviewed node operators. This redundant validation structure ensures no single point of failure exists during cross-chain transfers.

Chainlink CCIP Features Drive the Migration Decision

Chainlink CCIP uses Decentralized Oracle Networks by default to maintain security at the protocol level. This design removes the burden of security configuration from asset issuers like Re. The baseline protection is built in, not optional.

The protocol also includes native rate limits that act as circuit breakers during extreme conditions. These controls are designed to contain risk and prevent widespread contagion if a worst-case scenario occurs. Re cited these controls as a meaningful factor in its selection.

CCIP also carries a SOC 2 Type 2 attestation, a certification required by major financial institutions. That standard now applies to every reUSD transfer across chains, giving Re a compliance footing that matches institutional expectations.

Johann Eid, Chief Business Officer at Chainlink Labs, addressed the broader significance of the migration. “We’re excited to support Re as it upgrades to Chainlink CCIP as its exclusive cross-chain infrastructure to expand reUSD across chains,” Eid said.

He added that the move reflects a broader industry shift where leading protocols adopt Chainlink exclusively to provide the uncompromising security necessary to scale stablecoins across the multi-chain ecosystem.

Chainlink noted that Re is decommissioning its legacy bridging solution following an extensive security review.

The post Re Protocol Drops LayerZero for Chainlink CCIP as Exclusive Cross-Chain Bridge for reUSD appeared first on Blockonomi.