Ethereum Draft Proposes Sponsored Proof Batches

A community draft outlines general proof verification and sponsored claim aggregation for the Ethereum network.

Updated on Nov. 14, 2026 in Semiconductors

Ethereum Draft Proposes Sponsored Proof Batches

An Ethereum community draft proposes general proof verification and sponsored batches, enabling a sponsor to pay for an aggregated node containing multiple claims. The design builds on earlier Ethereum work on proof aggregation.

Why it matters

The draft aims to let multiple users share verification costs while paying only for the claims they submit. Activation would depend on performance benchmarks, so the proposal remains a draft rather than a finalized network change.

The draft reserves the LEANSTARK_SCHEME identifier under EIP-8288 and specifies verifier identity, resource boundaries and dependency digests. Any valid subset of claims can be included without re-signing, though no performance numbers are given.

The details

The draft lets a sponsor pay for an aggregated node containing multiple claims, while each member pays for the claims they submit. Any valid subset of claims can be included without re-signing, and the specification defines verifier identity, resource boundaries and dependency digests.

Timeline

  1. The draft is a current community proposal with no activation date identified in the source.

Roadmap

The proposal extends earlier Ethereum proof-aggregation work, including an EIP draft focused on transaction proofs across the mempool. It moves that line of research toward general-purpose verification with shared sponsorship.

For Ethereum users, the proposal could reduce the cost of verification by letting several parties share one sponsored batch. Users would still pay for the individual claims they submit, and the feature depends on future performance benchmarks.

The takeaway

Shared-cost proof batching could make verification cheaper for groups of users, but the design remains a draft until performance benchmarks justify activation. Readers should watch for changes as the specification develops.

Further reading

Explore more semiconductor and chip-level technology coverage for context on hardware underpinning digital systems.