web3wagmi
← All standards

EIP-8197 Cryptographically Agile Transactions

DraftCorecreated 2025-03-04requires EIP-1559, EIP-2718, EIP-2930, EIP-4844, EIP-7702

Cryptographically Agile Transaction format separating signature from transaction body

Authors: Danno Ferrin (@shemnon), Ron Kahat

Depends on (5)

Proposals this one names in its requires field.

EIP-1559Fee market change for ETH 1.0 chainEIP-2718Typed Transaction EnvelopeEIP-2930Optional access listsEIP-4844Shard Blob TransactionsEIP-7702Set Code for EOAs

What the specification covers

AbstractMotivationSpecificationParametersTransaction EncodingPayload Types and Data[EIP-7702](./eip-7702.md) Authorization ListSignaturesSignature HashSignature Type 0: ECDSAAddress DerivationReceiptsTransaction HashGas CostsRationaleSeparation of Format and Algorithm RegistryFlat StructurePayload-Controlled Signature CountTrailing vs. Embedded SignaturesCATX-Formatted AuthorizationsCATX Signature Domain SeparationChained Signature HashesLegacy Transaction ExclusionAddress Derivation and Cross-Scheme CollisionsReduced Signature ManipulationBackwards CompatibilitySecurity ConsiderationsSignature Algorithm BindingKey Substitution AttacksCross-Scheme Address CollisionsCATX Signature Domain SeparationAuthorization Signature MalleabilityCopyright

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