L2BEAT Bridges is a work in progress. You might find incomplete research or inconsistent naming. Join our discord to suggest improvements!
Beamer Bridge V2
| Website | beamerbridge.com |
|---|---|
| App | app.beamerbridge.com |
| Repository | github.com/beamer-bridge/beamer |
| Social | @BeamerBridgeDiscord@BeamerBridge |
...
Choose token
USD Coin (USDC)
Wrapped Ether (WETH)
Dai Stablecoin (DAI)
Tether USD (USDT)Beamer Bridge is an optimistic rollup-to-rollup bridge that enables direct ERC-20 asset transfers between any two EVM compatible rollups, without transitioning to L1.
It uses actors called Agents to fulfill user transfer requests on the destination chain. Users lock their assets on the source chain, and Agents provide the assets on the destination chain. Agents later receive the locked capital on the source chain by proving that they actually provided the assets on the destination chain. There is no liquidity pool, every agent participates in the cross-chain transfer by providing their own capital. Claims can ultimately be challenged on L1 using the rollups canonical bridges.
Principle of operation
The user initiates transaction to contract on Rollup 1, locking fees and assets. An Agent sends assets to user on Rollup 2. At this stage, the user is done and receives their assets on target rollup. The agent initiates the claim on the rollup, and if no one challenges the claim, the agent can withdraw the assets after 24h.
Optimistic validation with fallback to canonical bridge
Claims are considered valid if no challenge is submitted within the claim period (24h). The dispute can either be resolved by the participants using an auction system or escalated by making use of the canonical bridge.
Funds can be stolen if an agent claim is left unchallenged for 24 hours or the L1 dispute resolution is not triggered.
Destination tokens
Only tokens that have been bridged using native chain bridges are supported.
The system uses the following set of permissioned addresses:
Can invoke admin functions on the contracts such as adding new tokens, whitelisting agents or pausing the contracts.
Addresses allowed to fill requests.
The system consists of the following smart contracts:
This contract resides on the L1 chain and is tasked with receiving thefill or non-fill proofs from the target L2 chain and forwarding them to the RequestManager on the source L2 chain.
When a user wants to perform a transfer from Ethereum to a rollup they deposit their funds in the request manager. An agent fills the request on the target chain and can later claim the funds locked in the RequestManager. The contract is pausable by Owner. The contract is currently paused. This contract stores the following tokens: USDC, WETH, DAI, USDT.
Agents filling requests from a Rollup to Ethereum use this contract to transfer the funds to the user.
The Ethereum L2 Messenger stores messages coming from the FillManager for a potential future L1 resolution. It takes over the job of the canonical bridges for rollups which is storing all messages going from the FillManager to the Resolution contract on L1.
The Ethereum L1 Messenger contracts forwards messages to the RequestManager.
The messenger contracts establish an interface for communication with the RequestManager and FillManager contracts via the rollups. The Optimism L1 Messenger is responsible for relaying the messages to the Optimism chain.
The messenger contracts establish an interface for communication with the RequestManager and FillManager contracts via the rollups. The Arbitrum L1 Messenger is responsible for relaying the messages to the Arbitrum chain.
