L2BEAT Bridges is a work in progress. You might find incomplete research or inconsistent naming. Join our discord to suggest improvements!
Across V2
...
Choose token
Wrapped Ether (WETH)
USD Coin (USDC)
Wrapped BTC (WBTC)
Dai Stablecoin (DAI)
Tether USD (USDT)
Balancer (BAL)
UMA Voting Token v1 (UMA)
Boba Token (BOBA)Description
Across V2 is a cross-chain optimistic bridge that uses actors called Relayers to fulfill user transfer requests on the destination chain. Relayers are later reimbursed by providing a proof of their action to an Optimistic Oracle on Ethereum. The architecture leverages a single liquidity pool on Ethereum and separate deposit/reimburse pools on destination chains that are rebalanced using canonical bridges.
If you find something wrong on this page you can submit an issue or edit the information.
Risk summary
Funds can be stolen if
Funds can be lost if
Funds can be frozen if
Technology
Principle of operation
This bridge performs cross-chain swaps by borrowing liquidity from a network of Relayers who are then reimbursed on a chain of their choosing from a common liquidity pool (which consists of user deposits and deposits of independent Liquidity Providers). Specifically, when a user deposits funds for a swap into a dedicated pool on origin chain, a Relayer first pays the user on the requested destination chain and then shows proof of that deposit to Optimistic Oracle on Ethereum to be reimbursed. Liquidity used for reimbursements is rebalanced between a main pool on Ethereum (called Hub Pool) and pools on destination chains (called Spoke Pools) via native chain bridges.
Funds can be frozen if owner pauses the contract.
Funds can be lost if owner invokes a "haircut" functionality, dedicated for irrecoverable loss of funds on L2.
Validation via Optimistic Oracle
Money from the liquidity pool is used to reimburse Relayers based on a proof of deposit on destination chain that is provided to Optimistic Oracle on Ethereum. The proof can be disputed in a configured time period.
Funds can be stolen if a false claim to the Optimistic Oracle is not disputed in time.
Funds can be lost if a re-org occurs on destination chain after Optimistic Oracle dispute time passes.
Destination tokens
Only tokens that have been bridged using native chain bridges are supported.
Permissions
The system uses the following set of permissioned addresses:
Can invoke admin functions of HubPool contract, and by implication of other contracts. This is a Gnosis Safe with 3 / 5 threshold.
Those are the participants of the HubPool Multisig.
Allowed to propose BondToken transfers
Smart contracts
The system consists of the following smart contracts:
Escrow contract for ERC20 tokens and administration of other contracts. There is a 1h 30m delay before a bundle proposal is considered finalized. This contract stores the following tokens: USDC, WETH, WBTC, DAI, BAL, UMA, BOBA, USDT.
Token used to bond the data worker for proposing Relayer refund bundles.
This contract stores the following tokens: USDC, WETH, WBTC, DAI, BAL, UMA, BOBA, USDT.
