What is EIP-5792? A Guide to Ethereum’s Wallet Call API

In this blog post, we’ll explore EIP-5792 (Wallet Call API), a standardized protocol transforming how Ethereum applications interact with wallets. By introducing atomic transaction bundling and wallet capability discovery, EIP-5792 addresses critical pain points in decentralized application (dApp) development while unlocking new user experience (UX) possibilities. We’ll break down its technical components, real-world applications, and how tools like thirdweb’s Connect SDK simplify implementation for developers.

What Problem Does EIP-5792 Solve?

Ethereum’s wallet ecosystem has long been fragmented, creating challenges for developers and users alike:

1. Fragmented Wallet Integrations
   • Developers must write separate code paths for Externally Owned Accounts (EOAs) (e.g., MetaMask) and smart contract wallets (e.g., thirdweb Smart Wallets). This doubles integration work and limits cross-wallet compatibility.
2. Missing Standards for Batch Transactions
   • Common workflows like approving tokens before swapping require multiple user confirmations. Without atomic guarantees, failed transactions leave users paying gas fees for incomplete operations.
3. Limited Wallet Feature Discovery
   • dApps cannot programmatically detect wallet capabilities like gas sponsorship or batch execution support, leading to suboptimal default behaviors.

EIP-5792 eliminates these issues by standardizing:

• A unified API for all wallet types
• Atomic multi-step transactions
• Programmatic wallet capability checks

Core Technical Components of EIP-5792

1. wallet_sendCalls: Batch Transaction Submission

This JSON-RPC method allows dApps to submit multiple transactions as a single bundle:

{
"chainId": "0x1",
"from": "0x...",
"calls": [
{"to": "0x...", "value": "0x0", "data": "0x..."},
{"to": "0x...", "value": "0x0", "data": "0x..."}
],
"capabilities": {"paymasterService": {"url": "https://..."}}
}

Key features:

• Atomic Execution: All transactions either succeed or fail together, eliminating partial failures.
• Gas Sponsorship: Integrate paymasters via the capabilities field for gasless transactions.

2. wallet_getCallsStatus: Execution Tracking

Check the status of a transaction bundle using its bundleId:

• Returns CONFIRMED, FAILED, or PENDING
• Enables real-time progress tracking in UIs

3. wallet_getCapabilities: Feature Discovery

Query a wallet’s supported features:

{
  "atomicBatch": true,
  "paymasterService": true,
  "sessionKeys": false
}

This allows dApps to dynamically adjust workflows based on wallet capabilities.

Key Benefits of EIP-5792

1. 57% Gas Savings via Bundling

By batching transactions, Coinbase Smart Wallet users save 57% on gas costs compared to sequential single transactions.

2. Native Gasless Experiences

Integrate paymaster services directly into transaction bundles. For example, thirdweb’s Paymaster Service lets developers sponsor gas fees with one line of configuration:

capabilities: { paymasterService: { url: `https://${chainId}.bundler.thirdweb.com/${clientId}` } }

3. Future-Proof Compatibility

The abstracted API layer ensures compatibility with emerging wallet types, from ERC-4337 smart accounts to MPC wallets.

4. Simplified dApp Code

Developers write 40% less integration code (based on thirdweb metrics) by eliminating wallet-specific logic.

Use Cases Enabled by EIP-5792

DeFi: Single-Click Approve + Swap

Instead of two transactions (approve ERC-20 → swap), execute both as an atomic bundle. Users get a seamless experience, while developers reduce support tickets from failed approvals.

Gaming: Batch NFT Mints

Mint a character NFT, equip gear, and join a match in one atomic transaction. Platforms like thirdweb Smart Wallets achieve batch execution in 350ms, matching Web2 speed expectations.

DAOs: Multi-Step Governance

Execute governance proposals atomically—e.g., transfer funds + update protocol parameters—without partial execution risks.

Social: Sponsored Onboarding

Sponsor gas fees for new users via paymasters during onboarding flows, abstracting away blockchain complexities.

Impact on the Wallet Ecosystem

EIP-5792 elevates smart contract wallets to first-class citizens alongside EOAs:

1. Feature Parity: Smart wallets like thirdweb’s now offer superior UX (1-click transactions) without sacrificing EOA compatibility.
2. New UX Patterns:
   • Session keys for temporary transaction permissions
   • Automated subscription renewals via batched transactions
3. Enterprise Adoption: Atomic transactions reduce operational risks in high-value use cases like institutional DeFi.

Developer Implications

1. Unified API Across Wallets

thirdweb’s Connect SDK provides full EIP-5792 support:

import { sendCalls, getCapabilities } from "thirdweb/wallets/eip5792";  

// Send atomic batch
const { bundleId } = await sendCalls({  
  calls: [approveCall, swapCall],
  capabilities: { paymasterService: true }  
});  

// Track status
const status = await getCallsStatus({ bundleId });  

Supported wallets include Coinbase Smart Wallet, thirdweb In-App Wallets, and Smart Wallet v3+.

2. Automatic Fallbacks

The SDK automatically falls back to legacy methods (e.g., eth_sendTransaction) if a wallet doesn’t support EIP-5792.

3. React Hooks

Pre-built hooks simplify frontend integration:

const { mutate: sendCalls } = useSendCalls();  
const { data: status } = useCallsStatus({ bundleId });  

How to Implement EIP-5792 with thirdweb

1. Set Up the Connect SDK
   Install the SDK and configure supported wallets:

npm install thirdweb

1. Enable Gasless Transactions
   Add thirdweb’s Paymaster Service in your capabilities configuration:

capabilities: {
  paymasterService: {
    url: `https://${chainId}.bundler.thirdweb.com/${clientId}`
  }

1. Deploy Smart Wallets
   Use thirdweb’s Smart Wallet templates for native EIP-5792 support, including session key management.

For a step-by-step tutorial, explore thirdweb’s EIP-5792 Demo GitHub Repository.

Conclusion: The Future of Wallet Interactions

EIP-5792 marks a paradigm shift in Ethereum wallet standards, enabling atomic transactions, gasless flows, and seamless cross-wallet compatibility. By abstracting away low-level complexities, it empowers developers to build applications that are both user-friendly and future-proof.

Tools like thirdweb’s Connect SDK and Smart Wallets accelerate adoption, offering out-of-the-box EIP-5792 support, paymaster integrations, and atomic transaction bundling. As the ecosystem converges on this standard, users gain Web2-like simplicity, while developers unlock powerful new design patterns.

Start building with EIP-5792 today using thirdweb’s production-ready SDKs and infrastructure.