Bridging GEN (L1 ↔ L2)
GenLayer Chain is an Arbitrum Orbit L2. A deposit moves ERC-20 GEN on Ethereum to native GEN on GenLayer Chain. A withdrawal returns native GEN to Ethereum as ERC-20 GEN. Bradbury Phase 2 settles to Ethereum Sepolia and uses AnyTrust for data availability.
This guide follows a transfer through the canonical bridge from the first wallet signature to the balance change on the destination chain.
For Bradbury Phase 2, open the GenLayer testnet bridge on Rollbridge (opens in a new tab). Check that the route connects Ethereum Sepolia (11155111) and GenLayer Chain (4221). Verify the Phase 2 genesis hash and the Sepolia GEN token (opens in a new tab). If you cannot verify the route or token, stop before approving or sending GEN.
Before you start
Bridging touches two chains, so you need both set up:
- The GenLayer Chain (L2) in your wallet. Add it from the GenLayer Chain (L2) section on the Networks page (it includes an "add to wallet" control). GEN is the native token on this chain — balances are denominated in wei (1 GEN = 10¹⁸ wei).
- The corresponding L1 (Ethereum) network in the same wallet, holding the GEN you want to deposit plus a little of the L1 gas token to pay for the deposit transaction.
- Gas on both sides. A deposit costs L1 gas; a withdrawal costs L2 gas to initiate and then L1 gas to finalize/claim on Ethereum.
Use the bridge for your specific GenLayer deployment. An Arbitrum One or Nova bridge address belongs to a different chain.
Deposit: L1 → L2
Deposits are the fast direction. Bringing GEN from Ethereum onto the GenLayer Chain follows the standard rollup deposit flow:
- Connect your wallet to the Bradbury Phase 2 bridge (opens in a new tab) and select Ethereum Sepolia as the source. Use the wallet that holds your Sepolia GEN.
- Select the deposit direction (L1 → GenLayer Chain) and the amount of GEN.
- Approve and deposit the GEN. Check the spender and amount in the L1 token approval. Submit the native-token deposit through the chain’s ERC-20 Inbox.
- Verify the L2 credit. When the sequencer includes the deposit, check the recipient’s native GEN balance. A native GEN deposit uses a direct Inbox credit. Contract calls and messages can use retryable tickets.
Once the deposit lands on L2, your GEN is the native currency of the GenLayer Chain — you can transfer it, pay fees with it, or delegate it to a validator.
Withdraw: L2 → L1
A canonical withdrawal (opens in a new tab) requires a transaction on each chain.
- Initiate on L2. Select the L1 recipient and submit the withdrawal through the bridge. The L2 transaction uses
ArbSysto create an L2-to-L1 message. Save its transaction hash. - Claim on L1. Wait for the rollup assertion covering the message to be confirmed on Ethereum after the deployment’s challenge period. Once the message is executable, you or a relayer can submit its inclusion proof to the L1 Outbox. A successful execution releases ERC-20 GEN to the L1 recipient.
Check the message status before claiming. The L2 receipt and publication of the batch are earlier milestones. The wait depends on the deployment’s challenge period and assertion confirmation.
The GenLayer Finality Window governs appeals of Intelligent Contract results. The bridge uses the rollup assertion and the Outbox to determine when GEN can be claimed on Ethereum.
If the bridge offers a relayer, track its L1 execution transaction. Otherwise return to the bridge when the message becomes executable and submit the claim.
Track a transfer
Because a transfer spans two chains, you follow it on both:
- L2 side (GenLayer Chain). Use the Chain Explorer listed on Networks. Confirm the deposit credit or locate the withdrawal transaction and its L2-to-L1 message.
- L1 side (Ethereum). For a deposit, check the L1 deposit receipt and then confirm the L2 credit. For a withdrawal, find the successful Outbox execution on the parent-chain explorer and verify the recipient’s ERC-20 GEN balance.
- Bridge status page. If the network's bridge UI shows a transfer/withdrawal status (e.g. "ready to finalize"), that is usually the clearest signal for when a withdrawal's L1 claim step becomes available.
Keep the L2 withdrawal hash so you can find the message and claim it when its assertion is confirmed.
Common pitfalls
| Pitfall | What to do |
|---|---|
| Expecting a withdrawal to arrive as soon as the L2 receipt appears | Track the message until its assertion is confirmed and the Outbox claim succeeds. |
| Forgetting the L1 finalization step | A withdrawal is not complete until the L1 claim/finalize transaction succeeds. If your network's bridge doesn't auto-finalize, you must return and complete it. |
| No L1 gas to finalize | Keep some L1 gas token available to pay for the withdrawal's finalization transaction. |
| Using an address from another network | Match the route and Sepolia GEN token to the Bradbury links above. Verify the destination genesis hash on Networks. |
| Confusing GenLayer finality with L2→L1 settlement | Follow the appeal window for an Intelligent Contract result and the Outbox message status for a bridge withdrawal. |