Signature verification depends on more than receiving a signature: the accompanying witness data must also be checked. As reported on November 12, 2026, Ethereum developer Marchhill had submitted draft EIP-8437 to change how the eth/73 protocol handles that data. It was a proposal, not an adopted protocol change.
The draft proposes propagating Proof Wrappers through eth/73. An optional mode would let transactions submit raw signatures to an aggregator without first generating a STARK proof. It would also allow authenticated program packages to travel with transactions, so a specified program could run an independent check of witness data in a resource-limited sandbox. Under the proposal, new programs would not need a separate native adapter for each signature scheme.
The draft also calls for limits on batch-queue size, removal of expired transactions and a recheck of records before proof generation to support retries after failures.
EIP-8437 remained in Draft status and had not been merged at the time of the report. According to the developer, checks for VM and key-binding consistency, cryptographic validation and performance testing were still incomplete; benchmarking had not yet been done. Its proposed verification path should therefore not be treated as a deployed safeguard for wallet holders.