ERC-7821 primary sources — 2026-05-07

Project status in this pass

• No standalone ERC-7821 whitepaper or litepaper surfaced.
• The clearest source of truth was the draft ERC itself, backed by the raw ERC markdown, OpenZeppelin’s smart-account docs, and Vectorized’s BEBE README.
• The sources consistently frame ERC-7821 as the thinnest reusable execution interface for EIP-7702 delegation contracts rather than a full smart-account architecture.

Primary-source snapshots

1) Canonical ERC page

• URL: https://eips.ethereum.org/EIPS/eip-7821
• Key excerpt/signals:
  • The abstract defines ERC-7821 as a minimal batch executor interface for delegations.
  • The motivation says multiple EIP-7702 delegations from major vendors are expected and that delegation switching is risky and uneconomical.
  • The ERC says the standard complements EIP-5792 wallet_sendCalls by enabling capability detection and calldata preparation for atomic batch execution on EOAs.
• Why it mattered:
  • This is the clearest evidence that ERC-7821 belongs in the corpus as execution-boundary infrastructure between delegated EOAs, wallets, and dapps.

2) Raw ERC markdown

• URL: https://raw.githubusercontent.com/ethereum/ERCs/master/ERCS/erc-7821.md
• Key excerpt/signals:
  • The minimal interface is just execute(bytes32 mode, bytes calldata executionData) and supportsExecutionMode(bytes32 mode).
  • The standard only blesses a small set of batch modes: base single batch, optional opData single batch, and optional batch-of-batches.
  • The rationale explicitly says the goal is radical minimalism and fast adoption, especially for approve-plus-swap workflows.
• Why it mattered:
  • These details show that ERC-7821 is optimizing for the narrowest portable execution ABI that many delegation contracts can share.

3) ERC-7579 compatibility in the ERC text

• URL: https://raw.githubusercontent.com/ethereum/ERCs/master/ERCS/erc-7821.md
• Key excerpt/signals:
  • The ERC says it intentionally reuses execute and supportsExecutionMode from ERC-7579 for compatibility.
  • It does not require executeFromExecutor, unlike fuller ERC-7579 account implementations.
  • The mode layout explicitly inherits ERC-7579’s encoding scheme.
• Why it mattered:
  • This is the best signal that ERC-7821 is a bridge standard between modular smart-account tooling and EIP-7702 delegation contracts.

4) OpenZeppelin smart-account docs

• URL: https://docs.openzeppelin.com/contracts/5.x/accounts
• Key excerpt/signals:
  • OpenZeppelin describes ERC-7821 as the minimal batched-execution standard for accounts.
  • The docs say the implementation supports a single batch mode and give an example combining an account, SignerERC7702, and ERC7821.
  • The docs note that the batch encoding follows the same format as ERC-7579 execution.
• Why it mattered:
  • This is strong evidence that ERC-7821 is already being treated as implementation-facing ecosystem plumbing rather than a speculative draft with no downstream uptake.

5) Vectorized BEBE README

• URL: https://raw.githubusercontent.com/Vectorized/bebe/master/README.md
• Key excerpt/signals:
  • BEBE is described as a stateless ERC-7821-style batch executor contract for EOAs to delegate to via EIP-7702.
  • The README says BEBE is essentially ERC-7821 plus ERC-1271 isValidSignature behavior tied to the EOA.
  • It publishes a canonical deployment address for the executor.
• Why it mattered:
  • This is the clearest concrete illustration that ERC-7821 is intended to become a reusable execution shell for delegated EOAs, not just a paper abstraction.

Working conclusion

ERC-7821 is best cataloged as the minimal contract-side execution standard for EIP-7702 delegated EOAs. The decisive evidence in this pass was the draft ERC’s explicit complementarity with EIP-5792, its reuse of ERC-7579 execution semantics, OpenZeppelin’s implementation-facing documentation, and Vectorized’s BEBE example showing how the standard can become a portable batch executor shell across delegation vendors.