EIP-7702 Atomic Batch (sponsored EOA execution)

EIP-7702 Atomic Batch (sponsored EOA execution)

Run a batch of calls as an EOA, atomically, with the gas paid by a different account. The engine is script/tasks/atomicBatch7702.ts; this document is the policy around it.

The core idea

EIP-7702 lets an EOA temporarily adopt a contract's code via a signed authorization. We delegate the EOA to the canonical Multicall3 (0xcA11bde05977b3631167028862bE2a173976CA11, deployed at that address on every EVM chain) and call its aggregate3 — which issues each inner call with msg.sender == the EOA, reverting the whole tx if any call fails.

Because the sponsor signs and pays for the transaction while the authority (the EOA) only signs an off-chain authorization tuple:

• the authority never needs a native balance, and
• there is no separate funding transaction for anyone to observe or front-run.

That second property is what makes this the reliable way to extract a transaction from a compromised, actively-swept EOA: a sweeper bot only fires when the key receives native gas. With 7702 sponsorship no gas ever lands on the key, the bot stays idle, and the authority's nonce stays stable so the authorization can't be invalidated underneath you.

When to reach for this

• Rescue / act as a key that can't hold gas. A compromised EOA whose native is swept on arrival, or a key that's simply out of gas on a chain, needs to make exactly one privileged call (e.g. transferOwnership, renounceRole, approve). Sponsor it.
• Atomic multi-step from one EOA. Several calls that must all land in one transaction or not at all (approve-then-pull, transfer-then-register, migrate-then-verify).
• Gasless UX for an EOA we control. Sponsor pays; the EOA just signs.

When to skip

• Tron → interact-tron (no EIP-7702; different VM/address model).
• Chain without EIP-7702 live → the type-4 tx won't be accepted. The engine's dry-run estimateGas surfaces this. Fall back to a normal tx (fund the EOA) or an MEV-protected bundle if a sweeper is the problem.
• Governance actions that must go through the Safe + Timelock — never route those