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: sdk/evm/connect/guides/batch-requests.md
+17-16Lines changed: 17 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ These requests can be contract calls or other JSON-RPC methods (for example, sig
10
10
Despite being batched into one HTTP request, each call still requires individual user approval, and if any request is rejected, the entire batch fails.
11
11
12
12
:::info
13
-
"Batching" can also refer to [Wagmi contract read batching](../wagmi/interact-with-contracts.md#batch-contract-reads) or
13
+
"Batching" can also refer to [Wagmi contract read batching](./wagmi/interact-with-contracts.md#batch-contract-reads) or
14
14
[sending atomic batch transactions](send-transactions/batch-transactions.md) in MetaMask.
15
15
:::
16
16
@@ -29,44 +29,44 @@ When using `metamask_batch`, keep in mind the following:
29
29
30
30
- Even though the requests are batched, each individual request still requires user approval.
31
31
- If any request in the batch is rejected, the entire batch will fail.
32
-
:::
32
+
:::
33
33
34
34
The following is an example of batching JSON-RPC requests using `metamask_batch`:
0 commit comments