Open
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
NicNomadic
commented
Feb 20, 2026
| - If the target account is a user account (also known as an externally owned account), the sequencer creates a transaction that calls the [Tezos bridge precompiled contract](https://explorer.etherlink.com/address/0xff00000000000000000000000000000000000001) (`0xff0...0001`) that transfers the XTZ to the user account. | ||
| - If the target account is a smart contract or EIP-7702 smart account, the sequencer calls the Tezos bridge precompiled contract to queue but not execute a transaction to transfer the XTZ. | ||
| Then, any user can call the `claim` function to execute the transaction and send the XTZ to the smart contract or smart account and call its code. | ||
| An automated system run by Optimistic Labs monitors the calls the `claim` function on behalf of depositors, so the process is transparent to bridge users. |
Collaborator
Author
There was a problem hiding this comment.
Doesn't parse. Does it mean this:
Suggested change
| An automated system run by Optimistic Labs monitors the calls the `claim` function on behalf of depositors, so the process is transparent to bridge users. | |
| An automated system run by Optimistic Labs monitors the queued transactions and calls the `claim` function on behalf of depositors, so the process is transparent to bridge users. |
There was a problem hiding this comment.
The rewriting you propose makes the sentence more clear and accurate indeed.
| This change to the bridge introduces a breaking change in the events that are emitted as part of the bridging process. | ||
| The `deposit` event is now emitted by the [Tezos bridge precompiled contract](https://explorer.etherlink.com/address/0xff00000000000000000000000000000000000001) (`0xff0...0001`), not the null/system address. | ||
|
|
||
| For more information, see TODO BLOG POST. |
Collaborator
Author
There was a problem hiding this comment.
Mind inserting the link
NicNomadic
changed the title
rodibozman
reviewed
Mar 10, 2026
| 1. The sequencer reads the ticket and information about it from the delayed inbox, leaves the ticket in control of the Smart Rollup itself, and calls the null address precompiled contract (`0x000...000`) with the information. | ||
|
|
||
| 1. The null address precompile sends the information about the deposit to the FA bridging precompiled contract (`0xff0...0002`), which then emits a `QueuedDeposit` event which contains the `depositId` information needed to complete the transfer. | ||
| 1. The null address precompile sends the information about the deposit to the Tezos bridge precompiled contract (`0xff0...0002`), which then emits a `QueuedDeposit` event which contains the `depositId` information needed to complete the transfer. |
There was a problem hiding this comment.
Why was this change? FA bridge made sense, Tezos bridge feels ambiguous as there is also the XTZ bridge which is at a different address 0xff0...0001.
| 1. The sequencer requests the state of Etherlink from a Smart Rollup node and receives the delayed inbox. | ||
| 1. The sequencer creates a corresponding transaction on Etherlink to transfer XTZ from the [null address](https://explorer.etherlink.com/address/0x0000000000000000000000000000000000000000) to the user's address. | ||
| 1. The sequencer adds this transaction to an Etherlink block as in the usual transaction lifecycle described in [Architecture](/network/architecture). | ||
| 1. Depending on the target account, the sequencer handles the deposit in different ways: |
There was a problem hiding this comment.
It's not the sequencer that will handle it (directly) but the according kernel logic that was implemented, in particular the precompiled contract.
There was a problem hiding this comment.
We always refer as "the sequencer does X" in this file so maybe it makes sense to keep it consistent and leave it like that.
rodibozman
reviewed
Mar 10, 2026
| The withdrawal process (moving XTZ from Etherlink to tez on Tezos layer 1) follows these general steps: | ||
|
|
||
| 1. An Etherlink user sends XTZ and their layer 1 address to the [withdrawal precompiled contract](https://explorer.etherlink.com/address/0xff00000000000000000000000000000000000001) in the Etherlink Smart Rollup via an Etherlink EVM node. | ||
| 1. An Etherlink user sends XTZ and their layer 1 address to the [Tezos bridge precompiled contract](https://explorer.etherlink.com/address/0xff00000000000000000000000000000000000001) in the Etherlink Smart Rollup via an Etherlink EVM node. |
There was a problem hiding this comment.
Related to one of my previous thread, the ambiguity arises here, we refer twice to the Tezos bridge but for different addresses.
It should be the XTZ bridge here. It is a seperate address/precompile from the FA bridge.
|
The rest lgtm w.r.t. Etherlink 6.2's changelog. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Update the doc according to the 6.2 upgrade proposal.
NB: merge only when (and if) the proposal is voted successfully.