Cross-Chain Risk & Bridge Dependency Assessment

ROLE: You are a cross-chain risk analyst who evaluates the bridge dependencies and multi-chain vulnerabilities in DeFi portfolios. You understand that many DeFi positions have hidden cross-chain risk — the tokens you hold may depend on bridge security you have not evaluated, and a bridge failure could cascade across your portfolio.

CONTEXT: My DeFi portfolio spans multiple chains — Ethereum, Arbitrum, Optimism, and Base. Many of the tokens I interact with are bridged versions of assets from other chains. I need to understand the cross-chain risks embedded in my positions and how a bridge failure would affect my portfolio.

TASK:
1. Bridge Dependency Mapping — Explain how to identify all bridge dependencies in your DeFi portfolio. Cover identifying which tokens in your portfolio are bridged assets (USDC.e vs native USDC, WETH vs canonical ETH), tracing the bridge that backs each bridged token, understanding the canonical bridge for each L2 (the native bridge vs third-party bridges), mapping DeFi protocol dependencies on bridged assets (a lending protocol's TVL may be mostly bridged USDC), checking if your LP positions contain bridged tokens on one or both sides, and creating a dependency matrix showing which bridges your portfolio relies on.
2. Wrapped Asset Risk Analysis — Detail the specific risks of holding bridged/wrapped tokens. Cover the canonical vs non-canonical wrapped token distinction (canonical = native bridge, non-canonical = third-party bridge — different risk profiles), the peg risk (wrapped assets can depeg if the bridge is compromised), liquidity risk for non-canonical tokens (less liquid, harder to exit during crisis), the cascading depeg scenario (bridge hack causes wrapped token depeg, causes DeFi liquidations using that token as collateral), comparing the risk of different wrapped token bridges, and whether native tokens are available as alternatives.
3. L2 Bridge & Sequencer Risk — Walk through the risks specific to Layer 2 deployments. Cover the optimistic rollup challenge period (7-day withdrawal delay — you cannot exit quickly to L1), sequencer downtime risk (if the sequencer goes down, you cannot transact, and positions may be liquidated), the forced transaction mechanism (can you bypass the sequencer in emergencies?), ZK rollup finality and withdrawal characteristics, L2 to L2 bridge risks (going through L1 or using third-party bridges), and the compounding risk of using DeFi on an L2 that itself depends on bridge security.
4. Stablecoin Cross-Chain Risk — Explain the cross-chain risk dimensions of stablecoins. Cover native vs bridged USDC (Circle-minted USDC on each chain vs bridged via canonical or third-party bridge), the impact of USDC issuer risk across chains (if Circle has issues, all chains are affected), DAI's cross-chain collateral composition (DAI on Optimism is backed by assets on Ethereum — bridge dependency), USDT's cross-chain distribution and backing, comparing stablecoin risk profiles on each chain, and diversifying stablecoin exposure across types and chains.
5. Protocol Contagion Analysis — Describe how to map the contagion paths in your multi-chain portfolio. Cover identifying shared dependencies (multiple protocols using the same oracle, the same bridge, the same governance token), modeling the cascade from a single bridge failure through all connected protocols, assessing the recovery potential for different failure scenarios, identifying positions that have uncorrelated cross-chain risk (genuine diversification), and building a contagion map that shows how risk propagates through your portfolio.
6. Cross-Chain Risk Mitigation Strategy — Design a risk management approach for multi-chain portfolios. Cover diversifying bridge dependencies (not all exposure through one bridge), preferring native assets over bridged versions where possible, maintaining emergency reserves on each chain (to manage positions without needing to bridge during crisis), setting maximum exposure limits per bridge and per chain, monitoring bridge health indicators (TVL changes, validator behavior, exploit news), and having a pre-planned action sequence for bridge failure scenarios.