An Ethereum contributor has drafted a proposal that lets several transaction claims share one proof while keeping separate payments and signatures. The submission is a draft pull request with no EIP number or mainnet activation date, and its fees and limits remain provisional.
Ethereum contributor Marchhill submitted a draft proposal to the EIP repository on Nov. 13 that would let sponsors pay for batch proofs while member transactions pay for their own claims. The draft has not been adopted as an Ethereum network upgrade.
Sponsors and members would pay separately
A sponsor would cover each retained batch leaf, an individual proof component containing several claims. Member transactions would pay according to their own submitted claims.
Any builder could include any valid subset without asking members to sign again. The draft would also preserve individual transaction nonces and receipts, so sharing proof work would leave those records attached to the separate transactions.
Discounted claims and sponsor payments would go directly to block builders. Ordinary proofs covering a single statement would remain eligible for the public mempool, where transactions wait for inclusion in blocks.
The draft builds on EIP-8288
The proposal would activate the LEANSTARK_SCHEME reserved in EIP-8288, which Vitalik Buterin and Thomas Coratger authored. That EIP proposes aggregating cryptographic signatures and proofs outside Ethereum's main execution process, with a recursive STARK establishing their validity at block level.
Marchhill's submission also supersedes an earlier pull request, #12654.
Charges depend on calibration
The revision lists provisional charges of 15,400 gas for native verification and 572,000 gas for ordinary generic verification. It assigns 5,100 gas to the intrinsic proof share, 675,000 gas to a leaf payment and 4,200 gas to a batch claim. The figures require joint calibration, so they do not establish a final fee schedule or a confirmed saving for users.
Resource controls include a provisional block limit of 16,384 distinct dependencies, applied independently of gas. A leaf could contain up to 256 claims, while a proof step could have 16 inputs.
Activation would depend on measurements covering the complete processing schedule, late sponsor repair, and per-proof charges that fit within transaction gas limits. An invalidated sponsorship could waste a builder's work, and the submission says inclusion gas would not reimburse it.
Source: crypto.news
Trading involves risk.
Risk Disclaimer
