L2BEAT Bridges is a work in progress. You might find incomplete research or inconsistent naming. Join our discord to suggest improvements!

Connext (Legacy) logoConnext (Legacy)

This project is archived.
  • Total value locked
    $5.86 K0.02%
  • Destination
  • Validated by
  • Type
    Liquidity Network

  • ...


    Choose token

    Bridged Tokens (Top 15)

    USD Coin (USDC)
    Dai Stablecoin (DAI)
    Tether USD (USDT)
    Wrapped BTC (WBTC)


    Connext Bridge is a cross-chain bridge that performs atomic swap between user and a liquidity provider (on separate chains) to perform asset swap. Liquidity Providers (Routers) bid for user requests in an off-chain auction.

    If you find something wrong on this page you can submit an issue or edit the information.

    Risk summary

    Note: This project's overview requires more research and might not present accurate information. If you want to contribute you can edit the information on Github. Alternatively you contact the project team on Twitter and encourage them to contribute a PR.


    Principle of Operation

    Connext Bridge is a cross-chain bridge that uses liquidity providers that participate in an auction with each other to fulfill a user token transfer request. Specifically, when a user intends to perform a cross-chain token transfer, they initially broadcast this intent off-chain to Routers (which are registered and run by liquidity providers, with their liquidity kept in Connext Bridge escrow on selected chains). Routers that are able and willing to commit to fulfill the transfer need to respond off-chain with a bid during a short period of time. Upon selection of a bid, the user and the Router start a peer-to-peer atomic swap process. The user communicates with TransactionManager contract on the source chain to lock their tokens and commit to the selected bid. This event triggers selected Router to lock corresponding amount on the destination chain. The user waits for this event and then relays a signed message to the destination contract (via a Relayer) to claim those funds, while the Router uses the same signed message to claim funds on the source chain. There is a timeout for this process - when it passes, both the user and the Router can reclaim their locked funds.

    • Users can be censored if liquidity providers decide to never bid to fulfill transfers of a given user.

    • Funds can be frozen if liquidity provider (Router) decides to not cooperate, living user's funds locked for a limited period of time (e.g. 72 hours).


    A user and a Router (liquidity provider) engage in a peer-to-peer atomic swap process and both are expected to monitor each other’s actions during the “Prepare” (lock) and “Fulfill” (claim) phases. When a Relayer is used to send a message to the destination chain, the user needs to verify that it happens, and that it happens in a timely manner.

    1. Docstring for TransactionManager.sol


    The system uses the following set of permissioned addresses:

    Owner of TransactionManager 0x155B…9493

    Can add and remove Routers and supported assets.

    Smart contracts

    The system consists of the following smart contracts:

    TransactionManager 0x31eF…0A09

    Escrow and logic for cross-chain transactions. This contract stores the following tokens: USDC, USDT, DAI, WBTC.

    FulfillInterpreter 0x5b9E…149a

    Contract enabling execution of arbitrary calldata on a destination chain.

    Knowledge Nuggets