Accounts: L1<->L2 transactions

This section explores the methods which allow the account to send transactions among both L1 to L2 networks.

If you want some background on how L1<->L2 interaction works on zkSync, go through the introduction.

Full examples of actions below are available on the getting started page.

Deposit

Wallet, L1Signer and L1VoidSigner objects provide a deposit workflow. For more information, please refer to the method specification Deposit.

For a complete example of how to execute the deposit workflow, take a look at the following: Deposit ETH and ERC20 token.

Request execute

Wallet, L1Signer and L1VoidSigner objects provide an option to request execution of L2 transaction from L1. For more information, please refer to the method specification requestExecute.

Base cost

Wallet, L1Signer and L1VoidSigner objects provide an option to calculate base cost for L2 transaction. For more information, please refer to the method specification getBaseCost.

Claim failed deposit

Wallet, L1Signer and L1VoidSigner objects provide a claim fail deposit workflow. For more information, please refer to the method specification claimFailedDeposit.

Finalize withdraw

Wallet, Signer and L2VoidSigner objects provide a finalize withdraw workflow. For more information, please refer to the method specification finalizeWithdrawal.

Withdrawal

Wallet, Signer and L2VoidSigner objects provide a withdrawal workflow. For more information, please refer to the method specification Deposit.

For a complete example of how to execute the deposit workflow, take a look at the following: Withdraw ETH and ERC20 token.