This repository has been archived by the owner on Oct 3, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 813
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
feat: add swift documentation (#722)
Co-authored-by: Bojan Nikitovic <[email protected]> Co-authored-by: Dustin Brickwood <[email protected]> Co-authored-by: Dennis <[email protected]> Co-authored-by: MexicanAce <[email protected]>
- Loading branch information
1 parent
a70a517
commit f333a65
Showing
6 changed files
with
871 additions
and
3 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,37 @@ | ||
--- | ||
head: | ||
- - meta | ||
- name: "twitter:title" | ||
content: Swift SDK L1/L2 Transactions | zkSync Docs | ||
--- | ||
|
||
# Accounts: L1<->L2 Transactions | ||
|
||
This section explores the methods which allow the [account](./accounts.md) 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](../../developer-reference/l1-l2-interop.md). | ||
|
||
Full examples of actions below are available on the [getting started](./getting-started.md) page. | ||
|
||
## Deposit | ||
|
||
`WalletL1` and `Wallet` objects provide a deposit workflow. For more information, please refer to the method specification [`Deposit`](accounts.md#deposit). | ||
|
||
## Request execute | ||
|
||
`WalletL1` and `Wallet` objects provide an option to request execution of L2 transaction from L1. For more information, please refer | ||
to the method specification [`RequestExecute`](accounts.md#requestexecute). | ||
|
||
## Base cost | ||
|
||
`WalletL1` and `Wallet` objects provide an option to calculate base cost for L2 transaction. For more information, please refer to the | ||
method specification [`BaseCost`](accounts.md#basecost). | ||
|
||
## Claim failed deposit | ||
|
||
`WalletL1` and `Wallet` objects provide a claim fail deposit workflow. For more information, please refer to the method specification | ||
[`ClaimFailedDeposit`](accounts.md#claimfaileddeposit). | ||
|
||
## Withdrawal | ||
|
||
`WalletL2` and `Wallet` objects provide a withdrawal workflow. For more information, please refer to the method specification [`Withdraw`](accounts.md#withdraw). |
Oops, something went wrong.