Ethereum Draft Adds Sponsored Proof-Verification Batches

An Ethereum community draft proposes adding general proof verification and sponsored batches, with LEANSTARK_SCHEME reserved by EIP-8288 and activation contingent on performance benchmarks.

Under the design, a sponsor would pay for "an aggregated node containing multiple claims," while each member would pay according to the claims that member submits. The draft therefore assigns shared batch funding to sponsors and keeps member charges tied to individual submissions.

What does sponsored batching change?

The proposal introduces a two-part payment arrangement for aggregated verification. A sponsor covers the aggregate, and members pay for the claims they put forward. The division lets one payment sponsor several claims without requiring every member to carry the full batch cost.

The split is operational as well as technical. Sponsorship attaches to the shared aggregate, while member payment attaches to the claims that member submits. That separation gives sponsors a way to fund several claims at once while leaving each submitter responsible for its own item.

How can a valid subset enter the batch?

"Any valid subset of claims could be included without re-signing," the draft says. The rule lets the aggregate retain claims that satisfy validity requirements without another signature round from their submitters.

This separates claim validity from aggregate membership. Rather than treating a batch as indivisible, the design can include the valid claims within it. Signatures already attached to a valid subset need not be renewed when that subset enters the aggregate.

Which operational rules does the draft define?

The draft specifies verifier identity, resource boundaries and dependency digests:

• Verifier identity establishes who performs the verification.
• Resource boundaries constrain the resources available to the verification operation.
• Dependency digests represent the dependencies associated with the aggregate.

The proposal as described does not specify eligibility criteria, numerical resource limits or a digest format. It also identifies no client implementation or network deployment, leaving those implementation choices unspecified in the available description.

How does it differ from earlier aggregation work?

The proposal follows earlier Ethereum work on proof aggregation, including an EIP draft focused on transaction proofs across the mempool. The earlier work addressed transaction proofs, while this community draft centers on general proof verification.

The new draft also introduces sponsors and members as distinct participants in the cost arrangement. Earlier work supplied the proof-aggregation context; this proposal adds a mechanism for dividing batch costs between shared funding and individual submissions.

What must happen before activation?

Activation would depend on performance benchmarks. The draft therefore makes successful benchmark performance a condition for bringing sponsored batches into use, rather than presenting them as an already scheduled network upgrade.

The available details include no benchmark results, thresholds, test dates or deployment timetable. They also provide no monetary amount for sponsorship or member payment. The funding model is clear in structure, while its monetary terms and benchmark thresholds are not.

Who bears the cost?

Sponsors would pay for the shared aggregated node. At the member level, payment follows the claims submitted. In practical terms, sponsorship can support several claims without making every member responsible for the full aggregate.

The arrangement does not erase member-level obligations, because each member remains responsible for its own submissions. It changes who carries the shared batch cost, not whether submitters contribute to the cost of their claims.

The proposal’s immediate significance is a new division of payment and verification roles around proof aggregation. Its next concrete checkpoint is performance testing, because the draft ties activation to benchmarks rather than a fixed calendar launch.