- Date
- Views
- 1
- Reading time
- 2 мин.
Ethereum Draft Proposes Shared Proof Verification and Batch Payments

Ethereum contributor Marchhill submitted a draft proposal to the Ethereum Improvement Proposal repository on Nov. 13. The proposal would enable generic proof verification and sponsored batch processing, allowing multiple transaction claims to share a cryptographic proof while retaining separate payments, signatures, nonces and receipts.
The draft would activate the LEANSTARK_SCHEME reserved in EIP-8288 and establish rules for sponsored batches. Under the proposed system, a sponsor could pay for each retained batch leaf, while member transactions would pay for their own claims.
A block builder could include any valid subset of a batch without requiring the remaining members to sign their transactions again. Payment matching would be checked during block finalization, and recursive proofs would authenticate the sources used in the batch. Payments for discounted claims and sponsorship would go directly to block builders.
The proposal separates proof verification from payment confirmation. Ordinary proofs covering a single statement would remain eligible for Ethereum’s public mempool, where transactions wait for block inclusion. Individual transaction nonces and receipts would remain attached to the separate transactions even when their proof work was shared.
Marchhill’s submission replaces an earlier proposal, pull request No. 12654. It has no assigned EIP number, dedicated discussion thread or mainnet activation date. It remains a draft and has not been adopted as an Ethereum network upgrade.
The design builds on EIP-8288, authored by Vitalik Buterin and Thomas Coratger. That proposal describes a system in which transactions identify statements requiring verification and a recursive STARK proves their validity at the block level. STARKs allow a verifier to confirm that a computation was performed correctly without repeating the full computation. Recursion allows one proof to verify other proofs.
EIP-8288 currently reserves the generic leanSTARK scheme rather than allowing it to be used in dependency frames. Marchhill’s draft would enable that use and replace a basic data-hash statement with a stable digest representing a list of claims.
The draft lists provisional charges of 15,400 gas for native verification and 572,000 gas for ordinary generic verification. It also proposes charges of 5,100 gas for an intrinsic proof share, 675,000 gas for a leaf payment and 4,200 gas for a batch claim. The figures remain subject to joint calibration and do not establish a final fee schedule or confirmed savings for users.
Proposed resource controls include a limit of 16,384 distinct dependencies per block, applied separately from gas, along with an inclusion-list fit rule. A leaf could contain up to 256 claims, while a proof step could have 16 inputs. Neither limit would cap all claims or proof steps across a block.
Activation would depend on performance measurements covering the full processing schedule, late sponsor repair and per-proof charges that fit within transaction gas limits, including required overhead. The draft distinguishes measured results from individual nodes and single machines from modeled results using 16 workers. It also notes that a builder’s work could be wasted if sponsorship is invalidated and that inclusion gas would not reimburse that work.
The research is part of broader efforts to improve Ethereum’s cryptographic infrastructure. Earlier in November, Ethereum researcher Justin Drake outlined a target of December 2028 for the network’s post-quantum transition.
Follow developments in Ethereum and other blockchain networks, and use crypto market data to review cryptocurrency prices, trading volumes and market capitalization.
Share to
Published by




