# L2BEAT interoperability protocols

> Cross-chain protocols tracked by L2BEAT, with their type and the bridge types they use.

Token pages live at /interop/tokens/{id}/{issuer}/{symbol}, where {id} is case-sensitive and alone identifies the token. Token ids come from the database, so they are not listed here: take them from the token links on the protocol pages.

## Protocols (/interop/protocols/{slug})

- [Avalanche](https://l2beat.com/interop/protocols/avalanche): Canonical bridge, lock-and-mint. Canonical EOA-bridge between Ethereum and Avalanche without any onchain validation logic.
- [deBridge DLN](https://l2beat.com/interop/protocols/debridge-dln): Intent bridge, non-minting. Intent framework built on top of the deBridge messaging protocol.
- [Hyperlane Warp Routes](https://l2beat.com/interop/protocols/hyperlane-hwr): Multichain, burn-and-mint / lock-and-mint / non-minting. Multichain token framework using the highly modular and open Hyperlane message bridge.
- [Chainlink CCIP](https://l2beat.com/interop/protocols/ccip): Multichain, lock-and-mint / burn-and-mint / non-minting. Multichain token framework using the CCIP messaging protocol.
- [CCTP v1](https://l2beat.com/interop/protocols/cctpv1): Multichain, burn-and-mint. CCTP v1 is the first version of the Cross-Chain Transfer Protocol by Circle.
- [CCTP v2](https://l2beat.com/interop/protocols/cctpv2): Multichain, burn-and-mint. CCTP v2 is the second version of the Cross-Chain Transfer Protocol by Circle.
- [Relay](https://l2beat.com/interop/protocols/relay): Intent bridge, non-minting. Intent-based centralized bridge optimised for speed, multichain and multiasset support.
- [Gas.zip](https://l2beat.com/interop/protocols/gaszip): Intent bridge, non-minting. Intent-based centralised EOA bridge used for gas token transfers, optimised for speed and diverse chain support.
- [LI.FI](https://l2beat.com/interop/protocols/lifi): Intent bridge, non-minting. Intent protocol implemented by LI.FI, based on the Open Intents Framework (OIF).
- [LayerZero](https://l2beat.com/interop/protocols/layerzero): Multichain, burn-and-mint / lock-and-mint / non-minting. LayerZero OFT (omnichain fungible token) is a multichain token framework built on the modular, highly customizable LayerZero messaging protocol.
- [Axelar](https://l2beat.com/interop/protocols/axelar): Multichain, lock-and-mint / burn-and-mint / non-minting. Token bridge built on the Axelar messaging protocol, mostly used for the multichain axlUSDC token.
- [Axelar ITS](https://l2beat.com/interop/protocols/axelar-its): Multichain, burn-and-mint / lock-and-mint / non-minting. Axelar ITS (Interchain Token Service) is a multichain token framework built on the Axelar messaging protocol.
- [1inch Fusion+](https://l2beat.com/interop/protocols/fusionplus): Intent bridge, non-minting. HTLC-like cross-chain intent protocol built by 1inch.
- [Circle Gateway](https://l2beat.com/interop/protocols/circlegateway): Multichain, burn-and-mint. Chain abstraction protocol built by Circle.
- [Wormhole WTT](https://l2beat.com/interop/protocols/wormhole-wtt): Other, lock-and-mint / burn-and-mint. Minting token bridge built on top of the Wormhole message protocol.
- [Wormhole NTT](https://l2beat.com/interop/protocols/wormhole-ntt): Multichain, burn-and-mint / lock-and-mint. Multichain token framework using the Wormhole message bridge.
- [Mayan](https://l2beat.com/interop/protocols/mayan): Intent bridge, non-minting. Intent framework using the Wormhole message bridge.
- [Meson](https://l2beat.com/interop/protocols/meson): Intent bridge, non-minting. Liquidity bridge specialised on alt-L1s.
- [Across](https://l2beat.com/interop/protocols/across): Intent bridge, non-minting. Intent framework specialised on popular chains and assets, speed and security.
- [deBridge](https://l2beat.com/interop/protocols/debridge): Other, lock-and-mint. deBridge is a message bridge and lock-and-mint token bridge.
- [Stargate](https://l2beat.com/interop/protocols/stargate): Intent bridge, non-minting / lock-and-mint / burn-and-mint. Liquidity bridge focused on USD stablecoins and ETH using the LayerZero message bridge.
- [Celer cBridge](https://l2beat.com/interop/protocols/cbridge): Intent bridge, non-minting. Liquidity bridge whose transfers are filled from a liquidity pool and must be authorized by the Celer SGN signer quorum.
- [Butter Network](https://l2beat.com/interop/protocols/butternetwork): Intent bridge, burn-and-mint / non-minting. Liquidity bridge and messaging protocol using the MAP relay chain (an alt-L1) and its light-client network to verify cross-chain messages.
- [Free Tunnel](https://l2beat.com/interop/protocols/freetunnel): Multichain, burn-and-mint. Centralised multichain token framework built for large transfers only, specialised on the Bitcoin-adjacent DeFi ecosystem.
- [Base Solana Bridge](https://l2beat.com/interop/protocols/basesolbridge): Canonical bridge, lock-and-mint. Base's native lock-and-mint token and message bridge between Base and Solana.
- [Agglayer](https://l2beat.com/interop/protocols/agglayer): Canonical bridge, lock-and-mint / burn-and-mint. The canonical or trust-minimized bridge: Agglayer supports transfers to/from Ethereum as well as native interop within the Agglayer cluster of chains.

## Canonical bridges of scaling projects (/layer2s/projects/{slug})

Their interop data is on the scaling project page: /interop/protocols/{slug} redirects there.

- [Abstract](https://l2beat.com/layer2s/projects/abstract): Canonical bridge, lock-and-mint. The canonical or trust-minimized bridge: ZK stack uses canonical bridges to and from Ethereum, based on the security of validity proofs.
- [Arbitrum Canonical](https://l2beat.com/layer2s/projects/arbitrum): Canonical bridge, lock-and-mint. The canonical or trust-minimized bridge: Each Arbitrum stack chain uses the state validation mechanism of the underlying chain for its canonical bridge.
- [Base Canonical](https://l2beat.com/layer2s/projects/base): Canonical bridge, lock-and-mint. The canonical or trust-minimized bridge: Each OP stack chain uses the state validation mechanism of the underlying chain for its canonical bridge.
- [Celo Canonical](https://l2beat.com/layer2s/projects/celo): Canonical bridge, lock-and-mint. The canonical or trust-minimized bridge: Each OP stack chain uses the state validation mechanism of the underlying chain for its canonical bridge.
- [Gnosis Bridge](https://l2beat.com/layer2s/projects/gnosis): Canonical bridge, lock-and-mint / burn-and-mint. The canonical bridge between Ethereum and Gnosis Chain.
- [Ink Canonical](https://l2beat.com/layer2s/projects/ink): Canonical bridge, lock-and-mint. The canonical or trust-minimized bridge: Each OP stack chain uses the state validation mechanism of the underlying chain for its canonical bridge.
- [Lighter](https://l2beat.com/layer2s/projects/lighter): Canonical bridge, lock-and-mint. Canonical bridge between Ethereum and the Lighter perp DEX (zkSync-style priority queue), used by traders to deposit collateral and claim withdrawals.
- [Linea Canonical](https://l2beat.com/layer2s/projects/linea): Canonical bridge, lock-and-mint. The canonical or trust-minimized bridge: Validated with Linea's validity proof system but supporting external L1 yield sources.
- [MegaETH Canonical](https://l2beat.com/layer2s/projects/megaeth): Canonical bridge, lock-and-mint. The canonical or trust-minimized bridge: Each OP stack chain uses the state validation mechanism of the underlying chain for its canonical bridge.
- [OP Canonical](https://l2beat.com/layer2s/projects/op-mainnet): Canonical bridge, lock-and-mint / burn-and-mint. The canonical or trust-minimized bridge: Each OP stack chain uses the state validation mechanism of the underlying chain for its canonical bridge.
- [Polygon PoS](https://l2beat.com/layer2s/projects/polygon-pos): Canonical bridge, lock-and-mint. The canonical bridge.
- [RISE Canonical](https://l2beat.com/layer2s/projects/rise): Canonical bridge, lock-and-mint. The canonical or trust-minimized bridge: Each OP stack chain uses the state validation mechanism of the underlying chain for its canonical bridge.
- [Robinhood Chain Canonical](https://l2beat.com/layer2s/projects/robinhood): Canonical bridge, lock-and-mint. The canonical or trust-minimized bridge: Each Arbitrum stack chain uses the state validation mechanism of the underlying chain for its canonical bridge.
- [Unichain Canonical](https://l2beat.com/layer2s/projects/unichain): Canonical bridge, lock-and-mint. The canonical or trust-minimized bridge: Each OP stack chain uses the state validation mechanism of the underlying chain for its canonical bridge.
- [World Chain Canonical](https://l2beat.com/layer2s/projects/world): Canonical bridge, lock-and-mint. The canonical or trust-minimized bridge: Each OP stack chain uses the state validation mechanism of the underlying chain for its canonical bridge.
- [ZKsync Era](https://l2beat.com/layer2s/projects/zksync-era): Canonical bridge, lock-and-mint. The canonical or trust-minimized bridge: ZK stack uses canonical bridges to and from Ethereum, based on the security of validity proofs.
- [Hyperliquid](https://l2beat.com/layer2s/projects/hyperliquid): Canonical bridge, lock-and-mint. Canonical USDC bridge between Arbitrum and Hyperliquid L1, validated by a permissioned set of Hyperliquid validators.