Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions EIPS/eip-5792.md
Original file line number Diff line number Diff line change
Expand Up @@ -47,7 +47,7 @@ This object allows the applications to attach a capability-specific metadata to

The `atomicRequired` field specifies if a wallet is required to handle the batch of calls atomically or not. The wallet capacity to execute batch calls atomically is exposed through the built in `atomic` capability and can be sourced via `wallet_getCapabilities`..

Unless these requirements are explicitly overriden by a certain `capability`, the wallet must adhere to the following rules.
Unless these requirements are explicitly overridden by a certain `capability`, the wallet must adhere to the following rules.
Note that such a `capability` is not in the scope of this EIP and should be defined in its own ERC.

The wallet:
Expand Down Expand Up @@ -348,7 +348,7 @@ The valid JSON-RPC values for this `atomic` capability's only property, `status`

This capability is expressed separately on each chain and should be interpreted as a guarantee only for batches of transactions on that chain.

If the `atomic` capability is not present for a given chain, and unless it is explicitly overriden by another `capability` (not in scope of this EIP), it means that the wallet does not support batching for that given chain.
If the `atomic` capability is not present for a given chain, and unless it is explicitly overridden by another `capability` (not in scope of this EIP), it means that the wallet does not support batching for that given chain.

#### `atomic` Capability Specification

Expand Down
Loading