Bridge Dependencies

Chainlink CCIP

Cross-chain interoperability protocol
3 direct

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 Bridged Chainlink CCIP (LockReleaseTokenPool) TokenAdminRegistry maps apxUSD to pool `0x0e9c…5BB5` (LockReleaseTokenPool 1.6.1) — canonical apxUSD is escrowed on Ethereum; Base holds a bridged representation
Centrifuge JAAA direct Mints native Chainlink CCIP (2-of-2 MultiAdapter) Second half of the 2-of-2 quorum with LayerZero V2; a forged message reaching the Spoke could mint JAAA, but BOTH bridges must be compromised
Maple (syrupUSDC) direct Bridged Chainlink CCIP (LockReleaseTokenPool) LockReleaseTokenPool holds ~13% of supply on mainnet, backing bridged syrupUSDC on Base/Arbitrum/Solana

Circle CCTP

Native USDC burn-and-mint bridge
3 direct · 1 indirect

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

Omnichain messaging (OFT / OApp)
8 direct · 2 indirect

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 Transport LayerZero OFT (asset routes) The assessed asset is the V2 LP token, which is not bridged; Across integrates LZ OFT to move bridged assets through its own routes
Centrifuge JAAA direct Mints native LayerZero V2 (2-of-2 MultiAdapter) Spoke `0xEC35…25aB` holds `wards` mint authority on JAAA and mints on cross-chain message; 5 DVNs on the LZ side and a 2-of-2 quorum with CCIP mean BOTH bridges must be compromised
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

17 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.