Skip to main content
Defined in EIP-5792
The atomic capability specifies how wallets execute batches of transactions, providing guarantees for atomic transaction execution. When supported, all transactions in a batch must succeed together or fail together.

Parameters

string
required
The atomic capability status for the current chain and account.Possible values:
  • "supported": Wallet will execute all calls atomically and contiguously
  • "ready": Wallet can upgrade to atomic execution pending user approval
  • "unsupported": No atomicity or contiguity guarantees

Returns

object
The atomic capability configuration for the specified chain.

Example Usage

Error Handling

Use Cases

DeFi Operations

Atomic execution is crucial for DeFi operations where multiple steps must complete together:

NFT Minting with Payment

Error Handling

Handle atomic capability errors appropriately:

Relationship with EIP-7702

The atomic capability works with EIP-7702 to enable EOA (Externally Owned Accounts) to upgrade to smart accounts that support atomic transaction execution:

Best Practices

  1. Check Capabilities First: Always verify atomic support before requiring it
  2. Provide Fallbacks: Implement sequential execution as a fallback when atomic isn’t available
  3. Use for Related Operations: Only require atomicity for operations that must succeed together
  4. Clear Error Messages: Provide helpful error messages when atomic execution fails
The atomic capability is chain-specific. Always check support for the specific chain you’re targeting.
Apps should first check wallet capabilities using wallet_getCapabilities before sending requests requiring atomic execution.