Draft EIP-8437 proposes changes to eth/73 for signature witness data

Builders working on transaction witness verification could gain another way to submit signature data under draft EIP-8437. As reported by Odaily on November 12, 2026, at 12:21 p.m. UTC+8, Ethereum developer Marchhill proposed using the eth/73 protocol to propagate proof-wrapped data. An optional mode would let a transaction send its raw signature to an aggregator without first generating a STARK proof.

The proposal would also let an authenticated program package travel with a transaction. A specified program could then run an independent check in a resource-limited sandbox to verify witness data—the data used to support verification—without requiring a separate native adapter for each signature scheme.

For batch handling, the draft calls for limits on queue size, removal of expired transactions and a fresh check of records before proof generation to support retries after failures.

This is not an available upgrade: EIP-8437 remains a draft and has not been merged. Checks for consistency between the virtual machine and key binding, cryptographic validation and performance testing remain incomplete; benchmarking has not yet been done.

Further reading