Layer leap #1764
Layer leap #1764
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
|
||
| <PublicPreviewBannerPartial /> | ||
|
|
||
| ## Single click bridging from L1 to L3 is now possible with layer leap |
There was a problem hiding this comment.
I think we need a few sentences here to explain what layer leap is, why we built it, and how it is implemented.
|
|
||
| | Contract | Address | | ||
| | --------------------- | ----------------------------------------------------------------------- | | ||
| | Arb One L1Teleporter | https://etherscan.io/address/0xCBd9c6e310D6AaDeF9F025f716284162F0158992 | |
There was a problem hiding this comment.
Confirming that the addresses for Nova and Arb1 are indeed identical? If they are the same, then maybe we should add a italicized note/sentence that these are the same. Initial reaction from seeing this is that this is a typo
Also any reason why we have 2 rows instead of 1 if the addresses are the same?
|
|
||
| ## Launch details | ||
|
|
||
| _Key timelines & announcements_ |
There was a problem hiding this comment.
i think these sort of info should be much earlier in the page and more obvious. Perhaps a banner at the very top?
arbitrum-docs/build-decentralized-apps/token-bridging/layer-leap.mdx
Outdated
Show resolved
Hide resolved
| @@ -0,0 +1,84 @@ | |||
| --- | |||
| title: 'Layer leap contracts' | |||
There was a problem hiding this comment.
is it Layer Leap or layer leap?
| ### 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](https://github.com/offchainlabs/arbitrum-token-bridge/issues/new?assignees=&labels=feat%2ctriage&projects=&template=add-layerleap-request.yml&title=%5bfeat%5d%3a+enable+layer+leap+for+%3corbit+chain%3e). | ||
|
|
||
| - If you are not on the Arbitrum Bridge UI yet you can sign up by filling out this [GitHub Template](https://github.com/OffchainLabs/arbitrum-token-bridge/issues/new?assignees=&labels=feat%2Ctriage&projects=&template=add-orbit-chain-request.yml&title=%5Bfeat%5D%3A+), and then also fill out the template above. | ||
| - You can demo Layer Leap on the Arbitrum Bridge by bridging to [Rari](https://bridge.arbitrum.io/?destinationChain=rari-mainnet&sourceChain=ethereum) and [Proof of Play](https://bridge.arbitrum.io/?destinationChain=pop-apex&sourceChain=ethereum). |
There was a problem hiding this comment.
Perhaps a demo of Layer Leap should be one of the 1st things a user sees/reads in this page.
|
|
||
| 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?_ |
There was a problem hiding this comment.
This feels incomplete and I'd argue that, even if it were complete, this info should be available before we give the user a way to adopt it
|
|
||
| For non Arbitrum One L3s: | ||
|
|
||
| - To enable Layer Leap for your Layer 3 you can follow the Deployment Procedure defined [here](https://github.com/OffchainLabs/l1-l3-teleport-contracts/blob/main/docs/info.md). Before self deploying, let Offchain Labs know about your request! |
There was a problem hiding this comment.
What about for L3s on Nova? It's not clear to me without reading a bit more that a new contract deployment is what is required for L3s on Arb1 and Nova.
Also how does someone contact offchain labs here? We should add a contact link/form.
|
|
||
| - To enable Layer Leap for your Layer 3 you can follow the Deployment Procedure defined [here](https://github.com/OffchainLabs/l1-l3-teleport-contracts/blob/main/docs/info.md). Before self deploying, let Offchain Labs know about your request! | ||
|
|
||
| _Implementation requirements for RaaSes?_ |
There was a problem hiding this comment.
This probably be its own section since the entire page so far has been aimed at orbit chain owners
|
|
||
| _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 |
There was a problem hiding this comment.
Would probably prefer to see this hyperlinked. Also when we talk about retryables, we should refer to https://docs.arbitrum.io/how-arbitrum-works/arbos/l1-l2-messaging#retryable-tickets
This reverts commit 749ef46.
…ap.mdx Co-authored-by: Derek Lee <[email protected]>
|
|
No description provided.