Bridge Dependencies
Chainlink CCIP
Chainlink's cross-chain interoperability protocol. Messages are validated by the Chainlink DON with a Risk Management Network; tokens move via burn/mint or lock/mint token pools.
| Protocol / Token | Type | Model | Integration | Details | |
|---|---|---|---|---|---|
| | Apyx apxUSD | direct | TODO | Chainlink CCIP | Uses CCIP for cross-chain transfers (no LayerZero dependency) |
| | Centrifuge JAAA | direct | TODO | Chainlink CCIP (2-of-2 MultiAdapter) | Second half of the 2-of-2 quorum alongside LayerZero V2 |
| | InfiniFi | direct | TODO | Chainlink CCIP + LayerZero | Cross-chain support added in PR 224 |
| | Maple (syrupUSDC) | direct | Bridged | Chainlink CCIP (LockReleaseTokenPool) | LockReleaseTokenPool holds ~13% of supply on mainnet, backing bridged syrupUSDC on Base/Arbitrum/Solana |
Circle CCTP
Circle's Cross-Chain Transfer Protocol moves native USDC by burning on the source chain and minting on the destination, gated by Circle's off-chain attestation service. Using canonical CCTP removes third-party lock-and-mint bridge risk; the trust assumption reduces to Circle's availability and attestation finality.
| Protocol / Token | Type | Model | Integration | Details | |
|---|---|---|---|---|---|
| | Gauntlet gtUSDa | direct | Transport | Circle CCTP V2 (native burn/mint) | Bridges USDC across Base/Arbitrum/Optimism to Morpho |
| | Origin OUSD | direct | Transport | Circle CCTP V2 | Cross-chain strategies bridge ~42% of TVL to Base and HyperEVM |
| | Yearn yvUSD | direct | Transport | Circle CCTP V2 (CCTPStrategy) | Bridges USDC to Arbitrum (funded, ~3.5%) and Base (added, 0 debt); Katana uses AggLayer separately |
| | Flex | indirect | Transport | Collateral is yvUSD (which bridges via CCTP) |
LayerZero
Generic cross-chain messaging. Tokens bridge via the OFT / OFT-Adapter standard; security depends on the configured DVN (Decentralized Verifier Network) set and the token's mint/burn authority on each chain.
| Protocol / Token | Type | Model | Integration | Details | |
|---|---|---|---|---|---|
| | Across Protocol | direct | TODO | LayerZero OFT | Standard cross-chain transfers |
| | Cap stcUSD | direct | TODO | LayerZero vault component | |
| | Centrifuge JAAA | direct | TODO | LayerZero V2 (2-of-2 MultiAdapter) | 2-of-2 quorum with Chainlink CCIP; 5 DVNs on the LZ side |
| | fxUSD | direct | TODO | LayerZero OFT | Omnichain bridging |
| | InfiniFi | direct | TODO | LayerZero + Chainlink CCIP | Cross-chain support added in PR 224 |
| | Midas mHYPER | direct | Mints native | LayerZero OFT Adapter (MidasLzMintBurnOFTAdapter) | Adapter holds M_HYPER_MINT_OPERATOR_ROLE (mint has no onchain backing check) and the burn role |
| | Paxos USDG | direct | Mints native | LayerZero V2 OFT (OFTWrapper) | OFTWrapper is Supply Controller SC3 with 45M USDG mint capacity (~521 USDG/sec refill) — the bridge can mint native USDG |
| | Re (reUSD) | direct | Mints native | LayerZero OFT (ReMintBurnAdapter) | ReMintBurnAdapter holds a live cross-chain mint path on reUSD; active on Avalanche, Arbitrum, Base, BNB; 2.5M/24h rate limit |
| | Resolv RLP | direct | Bridged | LayerZero OFT Adapter | OFT Adapter `0x234c…d06c` escrows canonical RLP on Ethereum (133,516 RLP locked of 14.64M supply); remotes are bridged OFTs |
| | Resolv wstUSR | direct | Bridged | LayerZero OFT Adapter | OFT Adapter `0xab17…1978` escrows canonical wstUSR (406,723 locked, ~22% of supply); live on Arbitrum, Base, BSC, Bera, Soneium, HyperEVM, TAC |
| | Sky USDS | direct | Bridged | LayerZero V2 OFT Adapter | Adapter locks USDS for Solana + Avalanche (~48.7M locked) and does NOT hold `wards` on USDS — it cannot mint native USDS |
| | Fluid | indirect | Bridged | rsETH market exposure | Inherits rsETH's LayerZero OFT Adapter model (canonical rsETH escrowed on Ethereum) |
| | KernelDAO hgETH | indirect | Bridged | Wraps rsETH (Kelp DAO) | rsETH bridges via OFT Adapter `0x85d4…8Ef3`, which escrows 46,254 rsETH (~9.6% of supply) — it cannot mint native rsETH |
21 dependencies across 3 bridges. Each row links to its risk report. This table is maintained from the reports — see the report and reassessment workflows for how new bridge dependencies are added.