WIP more info about ABIs and events

Author: timothymcmackin

docs/bridging/bridging-fa-how.md

@@ -32,7 +32,7 @@ The process of bridging FA-compatible tokens from layer 1 to Etherlink (also kno
    For information about token access control, see [Token standards](https://docs.tezos.com/architecture/tokens#token-standards) on docs.tezos.com.
 
 1. The user calls the helper contract's `deposit` entrypoint.
-The request includes the amount of tokens to bridge, the address of the Etherlink Smart Rollup, and the user's Etherlink wallet address, but not the tokens themselves.
+The request includes the address of the Etherlink Smart Rollup, the user's Etherlink account address, and the amount of tokens to bridge, but not the tokens themselves.
 
 1. The token bridge helper contract stores the address of the Etherlink Smart Rollup and the user's Etherlink address temporarily.
 
@@ -55,6 +55,12 @@ The request includes the amount of tokens to bridge, the address of the Etherlin
 1. Any user can call the FA bridging precompiled contract's `claim` function, which causes the contract to call the ERC-20 proxy contract.
 For tokens supported by the bridge, an automated program calls the `claim` function for you.
 
+   You can call the `claim` function yourself with this ABI, using the `depositId` field from the event:
+
+   ```
+   claim(uint256 depositId)
+   ```
+
 1. The ERC-20 proxy contract mints the equivalent tokens and sends them to the user's Etherlink account.
 
 This diagram is an overview of the process of bridging tokens from layer 1 to Etherlink:
@@ -104,11 +110,11 @@ When a deposit is ready to be claimed, the FA bridging precompiled contract (`0x
 
 Field | Type | Description
 --- | --- | ---
-`ticket_owner` | address | ???
-`receiver` | address | The Etherlink account that will receive the claimed tokens
+`depositId` | uint265 | The ID of the bridging transaction that users need to claim the pending deposit
+`recipient` | address | The Etherlink account that will receive the claimed tokens
 `amount` | uint256 | The amount of tokens
-`inbox_level` | unit256 | ???
-`inbox_msg_id` | unit256 | The ID of the bridging transaction that users need to claim the pending deposit
+`timelock` | uint256 | ???
+`depositCount` | uint256 | ???
 
 ### `Deposit` event
 
@@ -128,7 +134,6 @@ TODO ^ This info from `etherlink/kernel_latest/evm_execution/src/fa_bridge/depos
 
 When an account initiates a withdrawal, the FA bridging precompiled contract (`0xff0...0002`) emits a `Withdrawal` event that includes the following information:
 
-
 Field | Type | Description
 --- | --- | ---
 `amount` | unit256 | The amount of tokens
@@ -138,7 +143,7 @@ Field | Type | Description
 
 ### TODO other events
 
-TODO other withdrawal events from `etherlink/kernel_latest/evm_execution/src/fa_bridge/withdrawal.rs`:
+TODO other withdrawal events from `etherlink/kernel_latest/evm_execution/src/fa_bridge/withdrawal.rs` but I'm not sure if these fields translate directly to the fields in the event because  they seemed to be different for the deposit events:
 
 ```rust
 alloy_sol_types::sol! {

docs/bridging/bridging-fa-transactions.md

@@ -52,12 +52,20 @@ Follow these steps to deposit FA-compliant tokens from layer 1 to Etherlink:
      --burn-cap 0.1
    ```
 
+   For reference, this is the Micheline type for the parameter for this transaction:
+
+   ```michelson
+   (pair %deposit (address %rollup) (pair (bytes %receiver) (nat %amount)))
+   ```
+
    The token bridge helper contract sends the tokens to the ticketer contract, which issues a ticket that represents the tokens.
    The token bridge helper contract sends that ticket to Etherlink.
 
+   When Etherlink receives that deposit, the FA bridging precompiled contract (`0xff0...0002`) emits a `QueuedDeposit` event that includes the `depositId` for the deposit, which is needed to claim the deposit; see [Event reference](/bridging/bridging-fa-how#event-reference).
+
 1. When the deposit is in an Etherlink block, call the FA bridging precompiled contract contract's `claim` function to cause the ERC-20 proxy contract to mint the tokens.
 
-   The address of the precompiled contract is `0xff00000000000000000000000000000000000002` and to call the function you can use the ABI `claim(uint256 depositId)`, where `depositId` matches the `depositId` that was emitted in a previous event for this transfer by the precompile (`QueuedDeposit(uint256 depositId, address recipient, uint256 amount, uint256 timelock, uint256 depositCount)`).
+   The address of the precompiled contract is `0xff00000000000000000000000000000000000002` and to call the function you can use the ABI `claim(uint256 depositId)`, where `depositId` matches the `depositId` that was emitted in a previous event.
 
    As a reference, here is an [example of the sequencer injecting a deposit](https://explorer.etherlink.com/tx/0x5a06fe64e880d6d1f53c243477cd5656204712f1543b607340996ad246158669) and here is an [example of the corresponding claim transaction](https://explorer.etherlink.com/tx/0xe017665cd7bfdef375a863114ac9f7ed2538da4d8584b0f1e0aa71ce96342aee).
 
@@ -69,6 +77,8 @@ Follow these steps to deposit FA-compliant tokens from layer 1 to Etherlink:
 
    :::
 
+   When the deposit has been claimed, the FA bridging precompiled contract (`0xff0...0002`) emits a `Deposit` event; see [Event reference](/bridging/bridging-fa-how#event-reference).
+
 To see the tokens in your Etherlink wallet, look up the ERC-20 proxy contract in a block explorer or use its address to manually add the tokens to your wallet.
 Because the Etherlink tokens are compatible with the ERC-20 standard, EVM-compatible wallets should be able to display them.