For anyone concerned with how transaction signatures are verified, the key distinction is that EIP-8437 is a proposal, not an active protocol change. In a notice published on November 12, 2026, at 12:21 p.m. UTC+8, Odaily reported that Ethereum developer Marchhill had submitted the draft, which had not been merged.
The proposal would use eth/73 to propagate proof-wrapped data. 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 designated program could run an independent check of witness data in a resource-limited sandbox. The aim is to avoid building a separate native adapter for every signature scheme.
The draft also calls for limits on batch-queue size, removal of expired transactions, and another check of records before proofs are generated to support retries after failures. VM and key-binding consistency checks, cryptographic verification, performance testing, and benchmarking remain unfinished. These proposed safeguards should not be treated as verified or deployed protections.
Source: odaily.news (originally published 2026-11-12 12:21 UTC+8)

