Summary: ERC-7821 is best cataloged as a minimal execution-interface standard for delegated EOAs, not as a full smart-account framework or wallet product. Its core contribution is to define the thinnest common execute and supportsExecutionMode surface that lets EIP-7702 delegation contracts expose atomic batch execution in a way that wallets, dapps, and smart-account tooling can detect and use consistently. The important categorization clue is that ERC-7821 tries to standardize the batch executor boundary while leaving authentication and richer policy logic deliberately open.
What it does:
Defines a minimal execute(bytes32 mode, bytes executionData) interface for atomic batched calls
Defines supportsExecutionMode(bytes32 mode) so frontends and wallets can detect whether a delegation contract supports the expected batch mode
Reuses ERC-7579 execution semantics and mode layout rather than inventing a separate execution envelope for EIP-7702 delegations
Standardizes a simple single-batch mode, an optional opData-aware single-batch mode, and an optional batch-of-batches mode
Recommends a concrete detection-and-call flow so frontends can support approve-plus-swap style EOA batching without repeatedly switching delegations
Leaves authorization policy open, aside from recommending that unauthenticated empty-opData execution should usually require self-calls or explicit authorized entry points
Key claims:
The draft ERC says the goal is a minimal batch executor interface for delegations, which places ERC-7821 at the execution boundary for EIP-7702 rather than in the broader account-abstraction architecture
The motivation says multiple major vendors are expected to ship EIP-7702 delegations and that delegation switching is risky and gas-costly, so a standardized execution interface reduces vendor lock-in and unnecessary delegation churn
The ERC explicitly says it complements EIP-5792 wallet_sendCalls, which is a strong signal that ERC-7821 should be read as the contract-side execution counterpart to wallet-side call batching APIs
The specification only standardizes atomic batched execution modes and deliberately omits ERC-7579’s executeFromExecutor, showing that the standard is optimizing for lowest-common-denominator adoption rather than full modular-account completeness
The rationale says its “North Star” is to get every decentralized exchange to support approve-plus-swap workflows for EOAs with delegations, which reveals the main mechanism value: making batched execution detectable and portable enough for mass frontend support
The interface allows optional opData and optional batch-of-batches mode, keeping authentication, paymaster logic, and multi-signer packaging extensible without fragmenting the base execution ABI
OpenZeppelin’s smart-account docs already describe ERC-7821 as the minimal batched-execution standard and show an EIP-7702 example that composes it with an account and signer, which is good evidence that the standard is becoming implementation-facing ecosystem plumbing
Vectorized’s BEBE README describes a stateless ERC-7821-style batch executor for EOAs delegated via EIP-7702, which is the clearest concrete illustration that ERC-7821 is meant to become a reusable execution shell rather than a single vendor wallet design
Whitepaper: No standalone ERC-7821 whitepaper or litepaper surfaced in this pass. The clearest current sources were the draft ERC, the raw ERC markdown, OpenZeppelin’s smart-account documentation, and Vectorized’s BEBE README; see ../../whitepapers/erc-7821-primary-sources-2026-05-07.md.