Summary: ERC-7902 is best cataloged as capability-negotiation infrastructure for advanced smart-wallet flows rather than as a bag of wallet feature flags or a thin extension to EIP-5792. Its core move is to standardize how an AA-aware dapp can ask a wallet to carry low-level execution parameters — EIP-7702 authorization, static paymaster data, validity windows, multidimensional nonce fields, and even gas-parameter overrides — inside the wallet-call surface. The important categorization clue is that ERC-7902 pushes those choices into a typed capability layer where the wallet remains the policy chokepoint: the dapp can propose highly specific AA behavior, but the wallet decides what to expose, how to warn, and whether the requested authority is safe to execute.
What it does:
Defines AA-specific capability objects that extend the EIP-5792 wallet capability model for wallet_sendCalls-style flows
Adds eip7702Auth so a wallet can generate an EIP-7702 authorization tuple for a specified EOA and delegation target as part of AA execution
Adds staticPaymasterConfiguration so a dapp can pass pre-resolved paymaster parameters instead of forcing the wallet to discover them dynamically
Adds validityTimeRange so a dapp can bound when an operation is valid after signing
Adds multiDimensionalNonce so a dapp can explicitly supply nonce-key and nonce-sequence components for ERC-4337-style semi-abstracted nonces
Adds accountAbstractionGasParamsOverride so tightly coupled or debugging-oriented apps can override AA-specific gas fields rather than relying entirely on wallet defaults
Requires AA actions in this context to happen on a single chain and atomically
Key claims:
The draft ERC says EIP-5792 already provides the extensible wallet-to-dapp capability model, and ERC-7902 exists to carry the AA-specific fields that ERC-4337 and ERC-7769 leave at a lower RPC layer.
The spec’s most important move is not just adding more knobs; it standardizes where those knobs live. Instead of each wallet or SDK inventing proprietary payloads for paymasters, 7702 authorization, nonce dimensions, or AA gas overrides, ERC-7902 tries to make those requests portable across AA-aware wallets.
The eip7702Auth capability makes the wallet the decisive trust boundary for EIP-7702 delegation. The ERC says wallets MUST maintain a strict shortlist of well-known and publicly audited delegation targets, which is a strong signal that ERC-7902 is fundamentally about wallet-side policy mediation, not just developer convenience.
The staticPaymasterConfiguration and gas-override capabilities are analytically useful because they reveal a deeper split in AA architecture: paymaster selection, fee sponsorship, and gas estimation do not have to stay hidden inside the wallet or bundler. ERC-7902 turns them into negotiable app-to-wallet surfaces.
The spec explicitly says accountAbstractionGasParamsOverride should generally be reserved for apps closely coupled to a specific protocol version or for debugging, which is important evidence that the authors see these fields as dangerous low-level controls rather than default UX parameters.
The validity-window and multidimensional-nonce capabilities also make replay and execution-order policy more legible. ERC-7902 is not only about paying gas or batching calls; it exposes timing, sequencing, and authorization shape as first-class wallet capabilities.
Alchemy’s wallet API docs already expose eip7702Auth through wallet_getCapabilities, and its EIP-7702 guide says 7702 mode is enabled by default while delegation and transaction signing are prepared together. That is strong implementation-facing evidence that ERC-7902 is becoming real wallet plumbing rather than remaining a purely theoretical draft.
The deepest comparison question this adds to the corpus is whether AA standardization actually commoditizes wallet behavior, or instead recentralizes power in whichever wallets decide which capability objects, delegation targets, paymasters, and override paths are acceptable.
Whitepaper: No standalone ERC-7902 whitepaper or litepaper surfaced in this pass. The clearest current sources were the draft ERC, the raw ERC markdown, and implementation-facing wallet API docs that already surface eip7702Auth; see ../../whitepapers/erc-7902-primary-sources-2026-05-15.md.