Skip to main content

Layer Leap contracts

PUBLIC PREVIEW DOCUMENT

This document is currently in public preview and may change significantly as feedback is captured from readers like you. Click the Request an update button at the top of this document or join the Arbitrum Discord to share your feedback.

Single click bridging from L1 to L3 is now possible with layer leap​

Contract Addresses

ContractAddress
Arb One L1Teleporterhttps://etherscan.io/address/0xCBd9c6e310D6AaDeF9F025f716284162F0158992
Arb Nova L1Teleporterhttps://etherscan.io/address/0xCBd9c6e310D6AaDeF9F025f716284162F0158992

Launch details​

Key timelines & announcements

Orbit Onboarding: We are looking for interested Orbit L3s with ETH gas for immediate rollout AND Orbit L3s with custom gas tokens for future adoption in our next release.

Upcoming launches & future releases

A future release of Layer Leap is not yet scheduled, but upcoming features including providing support for Orbit L3s with custom gas tokens.

Value & user impact​

End-users: Can now bridge ETH and ERC-20s from Ethereum to your Orbit L3 in a single click.

  • Bridging ETH requires one call on L1
  • Bridging an ERC-20 requires one approval and one call on L1

Orbit L3s: Can more seamlessly onboard ETH and ERC-20s from Ethereum mainnet.

Which Orbit configurations can adopt this feature?

Any L3 Orbit Chains on top of an Arbitrum chain with ETH gas fees can use Layer Leap.

  • Layer Leap contracts are currently only deployed for Arb One and Arb Nova, but contracts can be deployed for additional Arbitrum Layer-2s by Offchain Labs or your RaaS provider.
    • The Layer 2 must be an Arbitrum chain due to the use of retryables.
  • Future support: Layer Leap will support Orbit chains with custom gas tokens in a future release

Implementation​

How can Orbit chains adopt this feature?

UI Adoption: Layer leap contracts can be integrated into your own bridge or added to your chain’s UI for the Arbitrum bridge (bridge.arbitrum.io)

Arbitrum bridge UI: if you are already on the arbitrum bridge UI then you can sign up for layer leap adoption by using this github template.​

  • If you are not on the Arbitrum Bridge UI yet you can sign up by filling out this GitHub Template, and then also fill out the template above.
  • You can demo Layer Leap on the Arbitrum Bridge by bridging to Rari and Proof of Play.

Custom bridge UI: if you want to integrate layer leap functionality into your custom bridge UI, read the info page on the layer leap github to learn more.​

What chains are currently supported?

Layer Leap requires an L1 teleporter contract for each L2 chain. L1Teleporter contracts are deployed on Ethereum L1 for Arb One and Arb Nova.

ContractAddress
Arb One L1Teleporterhttps://etherscan.io/address/0xCBd9c6e310D6AaDeF9F025f716284162F0158992
Arb Nova L1Teleporterhttps://etherscan.io/address/0xCBd9c6e310D6AaDeF9F025f716284162F0158992

For non Arbitrum One L3s:

  • To enable Layer Leap for your Layer 3 you can follow the Deployment Procedure defined here. Before self deploying, let Offchain Labs know about your request!

Implementation requirements for RaaSes?

Sending tokens from L2 to L3 relies on creation of a retryable. If you are supporting Layer Leap for your Orbit chains it’s highly recommended to be running the Retryables Monitoring tool: https://github.com/OffchainLabs/arb-retryables-monitoring. This will allow you to track and redeem any failed retryables

What configuration options or parameter changes should I consider?