L1<->L2 Transactions - ZKsync SDK Docs

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.

Deposit

Wallet and L1Signer 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 and L1Signer 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 and L1Signer objects provide an option to calculate base cost for L2 transaction. For more information, please refer to the method specification getBaseCost.

Withdrawal

Wallet and Signer 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

ZKsync Era Features

An overview of ZKsync Era features

Introduction

Overview of Web3Providers and their functions.