Skip to content

Reference information for FA bridging calls and events#367

Open
timothymcmackin wants to merge 10 commits intomainfrom
fa-bridge-events
Open

Reference information for FA bridging calls and events#367
timothymcmackin wants to merge 10 commits intomainfrom
fa-bridge-events

Conversation

@timothymcmackin
Copy link
Collaborator

@timothymcmackin timothymcmackin commented Sep 18, 2025

Provide more detailed information about how the FA bridge works. I took information about the events from etherlink/kernel_latest/revm/contracts/fa_bridge.sol but I'm not sure if I've got each field explained clearly.

@timothymcmackin timothymcmackin self-assigned this Sep 18, 2025
@vercel
Copy link

vercel bot commented Sep 18, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
docs-etherlink Ready Ready Preview, Comment Jan 30, 2026 4:43pm

Request Review

Field | Type | Description
--- | --- | ---
`ticketOwner` | address | The ERC-20 proxy contract that manages the tokens
`receiver` | address | The ERC-20 proxy contract that manages the tokens (a duplicate of the `ticketOwner` field)
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is untrue, it is the etherlink account receiving the FA deposit tokens

`sender` | address | The Etherlink address that is withdrawing the tokens
`ticketOwner` | address | The ERC-20 proxy contract that manages the tokens
`receiver` | bytes22 | The layer 1 address that receives the tokens
`proxy` | bytes22 | The proxy address through which the deposit is routed
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This might confusing w.r.t. other proxy mentions in the doc, this a L1 contract, in previous events proxy refers to a L2 contract

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Which contract is this, the token brige helper contract, the ticketer contract, or something else?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Based on discussion this appears to be the token bridge helper contract.


Field | Type | Description
--- | --- | ---
`ticketOwner` | address | The ERC-20 proxy contract that manages the tokens
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ticketOwner can sometimes be the receiver, but imho this is an implem detail and shouldn't be mentionned, I'll let you be the judge of it

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll add "or, in some cases, the account receiving the deposited tokens"

`sender` | address | The Etherlink address that is withdrawing the tokens
`ticketOwner` | address | The ERC-20 proxy contract that manages the tokens
`receiver` | bytes22 | The layer 1 address that receives the tokens
`proxy` | bytes22 | The proxy address through which the deposit is routed
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same remark here, find it confusing

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants