You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: wallet/how-to/send-transactions/send-batch-transactions.md
+10-2Lines changed: 10 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ You can send and manage batch transactions in MetaMask, using the methods specif
14
14
## About atomic batch transactions
15
15
16
16
An atomic batch transaction is a group of transactions that are executed together as a single unit.
17
-
When a dapp requests to submit a batch of transactions atomically, MetaMask may prompt users to upgrade their externally owned account (EOA) to a [MetaMask delegator account](https://docs.gator.metamask.io/concepts/delegator-accounts).
17
+
When a dapp requests to submit a batch of transactions atomically, MetaMask may prompt users to upgrade their externally owned account (EOA) to a [MetaMask delegator account](https://docs.gator.metamask.io/concepts/delegator-accounts) (or "smart account").
18
18
If the user accepts, MetaMask proceeds to upgrade the account and process the request as a single atomic transaction as specified by [EIP-7702](https://eips.ethereum.org/EIPS/eip-7702).
19
19
20
20
:::note Delegator accounts
@@ -81,7 +81,7 @@ For example:
81
81
The `atomic` capability can have a `status` of `supported` or `ready`:
82
82
83
83
-`supported` means MetaMask supports atomic batch transactions for the account and chain ID.
84
-
-`ready` means MetaMask will prompt the user to upgrade their account to a MetaMask delegator account.
84
+
-`ready` means MetaMask will prompt the user to upgrade their account to a MetaMask smart account.
85
85
If the user approves, the `status` will upgrade to `supported`.
86
86
87
87
If the `atomic` capability is not `supported` or `ready` for a specified chain ID, MetaMask will not return anything for that chain ID.
@@ -212,3 +212,11 @@ In some cases, calls can be executed atomically but in multiple transactions (fo
212
212
`eth_bundle` on an L2 network resistant to reorgs).
213
213
In these cases, `atomic` is `true` but multiple receipts are returned.
214
214
:::
215
+
216
+
## Resources
217
+
218
+
- See the [MetaMask 7702/5792 Readiness dapp](https://7702playground.metamask.io/) to quickly test sending batch transactions.
219
+
- See the [MetaMask Delegation Toolkit documentation](https://docs.gator.metamask.io/) for more information about delegator accounts and their capabilities.
220
+
- See the following topics in the MetaMask end user documentation:
221
+
-[What is a smart account?](https://support.metamask.io/configure/accounts/what-is-a-smart-account/)
222
+
-[How to switch to or revert from a smart account](https://support.metamask.io/configure/accounts/switch-to-or-revert-from-a-smart-account/)
0 commit comments