Ethereum’s eth/73 Draft Adds Raw-Signature Proof Wrappers

A draft Ethereum proposal, identified as eth/73, would let aggregators receive proof wrappers containing raw signatures before a full STARK proof is supplied, according to the draft published by the Ethereum community. It remains in draft status.

The proposal adds an optional mechanism called “Mode 2.” In that mode, an aggregator can receive a raw signature before the corresponding full proof arrives. The draft does not treat the raw signature as a replacement for the STARK proof. It changes the order of receipt and proof completion.

The early submission would be checked through metered sandbox execution. A fixed program would run against the witness data, letting the aggregator test the submission before the full proving step.

The published draft does not identify the fixed programs, the witness fields they inspect or how metering is configured. It also does not say the sandbox produces the STARK proof. Its stated role is narrower: checking witness data.

What does this change for aggregators?

The practical change is the intake sequence. An aggregator would not have to withhold receipt of a raw signature until a full STARK proof is available, because the proposed sandbox check could occur first. It could then move the submission into the later proving stage.

Mode 2 remains optional. The draft does not require every aggregator or submission to use the route. For operators that adopt it, the design makes proof preparation a staged process: early receipt, fixed-program witness checking, then proving.

The business effect is operational, not promotional. Aggregators could begin processing raw-signature submissions earlier while still managing validation, queues and retries. That is the clearest promise in the draft.

The published material does not identify participating aggregators, implementation teams, users or a deployment schedule. It also sets out no fee, revenue-sharing arrangement or token-level consequence. The proposal therefore targets a technical workflow, not an announced commercial arrangement.

Controls around the proof pipeline

The draft pairs the new intake mode with four controls for the proof process:

• Limit batch queues.
• Remove expired transactions.
• Check records again before proving.
• Provide a way to retry submissions.

These steps give the proposed pipeline several checkpoints. Queue limits manage pending work. Expiry rules clear transactions that have expired. The pre-proving check tests records after they move through the workflow. The retry path preserves a route for resubmission.

The published text gives no queue sizes, expiry periods, record contents or retry limits. It also does not explain in detail how these controls interact with Mode 2. Their placement within the broader proving process is clear; their operating parameters are not.

What remains unresolved

The draft’s central claim is precise: aggregators could receive raw-signature proof wrappers earlier, subject to an optional sandbox check, without waiting for a full STARK proof at intake. The surrounding controls govern how submissions then move toward proving, through queue limits, expired-transaction removal, renewed record checks and retries.

Until eth/73 advances beyond draft, its significance remains design work rather than an announced service change. A finalized specification would need to resolve how Mode 2 metering, wrapper validation and proof-stage controls work in practice before operators could judge the change.

With no activation date attached, eth/73 cannot alter aggregator operations until it leaves draft status and its implementation details are settled.