web3wagmi
← All standards

EIP-8202 Scheme-Agile Transactions

DraftCorecreated 2026-03-22requires EIP-2, EIP-155, EIP-1559, EIP-2718, EIP-2780, EIP-4844, EIP-7702, EIP-7976

A new EIP-2718 transaction type with a common EIP-1559 fee header, scheme-agile sender authorization, and flat typed extensions

Authors: Giulio Rebuffo (@Giulio2002), Ben Adams (@benaadams)

Depends on (8)

Proposals this one names in its requires field.

EIP-2Homestead Hard-fork ChangesEIP-155Simple replay attack protectionEIP-1559Fee market change for ETH 1.0 chainEIP-2718Typed Transaction EnvelopeEIP-2780Resource-based intrinsic transaction gasEIP-4844Shard Blob TransactionsEIP-7702Set Code for EOAsEIP-7976Increase Calldata Floor Cost

What the specification covers

AbstractMotivationStop proliferating top-level transaction familiesNative quantum-safe supportFlat composition, not recursive compositionSpecificationConstantsTransaction EnvelopeField DefinitionsAuthorization and Extension ContainersSigning DataScheme RegistrySignature Schemessecp256k1 (0x00)Ephemeral secp256k1 (0x01)Account SetupWitness PayloadSigningVerification and Address DerivationKey Material SummaryWhy This Is Quantum-SafeExtensionsBlob Extension (EXT_BLOB = 0x01)Set-Code Extension (EXT_SET_CODE = 0x02)Set-Code Gas AccountingTransaction ValidationReceiptRationaleWhy a single outer transaction type?Why make scheme agility an authorization capability?Why flat extensions instead of nested transactions?Why no access list in the base type?Why preserve the legacy secp256k1 address?Why hash scheme_id into non-secp256k1 addresses?Why include an ephemeral secp256k1 scheme?Why spell out the set-code extension instead of inheriting [EIP-7702](./eip-7702.md) by reference?Backwards CompatibilityTest CasesSecurity ConsiderationsAddress collision across schemesUnknown capability handlingFlat composition reduces validation complexityQuantum migration timingMempool exposure for ephemeral secp256k1Ephemeral key exhaustionLarge witness DoSSet-code non-rollbackDowngrade attacksKeccak-256 and post-quantum security marginCopyright

This proposal declares no Solidity interface, so there is nothing to compute. It may be a core protocol change, a meta proposal, or written in prose only.

Compare with

Parsed from the canonical specification · discussion