Ethereum proposal aims to enable batched shared proof payments

icon币界网
Share
AI summary iconSummary
Ethereum news: Developer Marchhill has proposed a new mechanism to support shared proof verification and sponsored batch processing. The draft enables multiple claims to use a single proof while preserving individual payments and signatures. Sponsors cover the cost of batch leaves, while participants pay for their own claims. The Ethereum ecosystem news update notes that the proposal is still under development and has not yet been approved for network adoption.
CoinMarketCap reports:

Ethereum contributor Marchhill has submitted a draft proposal aimed at supporting generic proof verification and sponsored batch processing, enabling multiple transaction claims to share a single proof while maintaining their individual payments and signatures.

  • Sponsors can pay for batch proofs, while members within the batch pay fees for their individual claims.
  • A valid subset can enter a block without members needing to re-sign their transactions.
  • The proposed fees and resource limits are still tentative and will be enabled based on performance measurements.
  • This submission is only a draft pull request and has not yet been assigned an EIP number or a mainnet activation date.

This proposal, submitted by Marchhill to the Ethereum EIP repository on November 13, will activate the LEANSTARK_SCHEME reserved in EIP-8288 and introduce sponsored batch rules. The submission is still under development and has not yet been adopted as an Ethereum network upgrade.

This draft consolidates generic verification, proof identifiers, resource limits, dependency summaries, and batch payments into a single proposal. It supersedes the earlier submission, pull request #12654, but the EIP number and dedicated discussion thread are still pending assignment.

Ethereum batch proofs will separate sponsors from member payments.

The core of this draft is a payment arrangement: sponsors pay fees for each reserved batch leaf, where a batch leaf is a single proof component containing multiple claims. Member transactions are charged based on their respective submitted claims.

Builders can include any valid subset without requiring members to sign again. Therefore, a transaction that is ready to be included in a block does not need a new signature simply because other members from the original group are excluded, as the proposal mechanism specifies.

The draft will retain the nonce and receipt for each individual transaction. The nonce identifies the position of the transaction within the account's transaction sequence, while the receipt records its execution result. Shared proof-of-work will not alter these records; they will remain attached to their respective individual transactions.

Payment matching will be verified during the final confirmation stage, while recursive proofs are used to validate the sources used in the batch. This submission separates two tasks: proving the validity of claims and confirming that the necessary payments have been accompanying them.

Discount claims and sponsor payments will flow directly to block builders. Ordinary proofs covering a single statement can still enter the public mempool, where transactions await inclusion in a block.

Universal Verification is built on EIP-8288.

The underlying EIP-8288, written by Vitalik Buterin and Thomas Coratger, proposes moving cryptographic signatures and proofs off the main Ethereum execution layer. Transactions will identify the statements they require verification for, while recursive STARKs will prove their validity at the block level.

STARK is a cryptographic proof that demonstrates a computation has been correctly performed without requiring each verifier to repeat the calculation. Recursion allows one proof to verify other proofs and combine their results.

EIP-8288 currently retains the generic leanSTARK scheme rather than allowing its use within dependent frames. Marchhill’s submission proposes enabling this path and replacing the raw data hash statement in the base draft with a stable digest representing a list of claims.

This design builds on previous discussions about cryptographic verification, including Buterin’s support for using aggregated proofs to handle complex cryptography. His comments address the underlying architecture, while Marchhill’s draft proposes a specific verification and payment arrangement.

The proposed fees still require calibration.

The revised version lists the tentative gas fees: 15,400 gas for native verification, and 572,000 gas for general universal verification. It allocates 5,100 gas to the intrinsic proof share, 675,000 gas to leaf payments, and 4,200 gas to batch claims.

Leaf payments are charged separately because binding payments add a fixed amount of work beyond standard verification, as explained in the draft.主张 and payments do not generate additional intrinsic proof shares. These figures require joint calibration and therefore do not constitute a final fee schedule, nor do they guarantee that users will save on fees.

Resource control includes a provisional block limit of 16,384 distinct dependencies, independent of gas computation, along with corresponding inclusion-list adaptation rules. A leaf may contain up to 256 claims, and a proof step may have up to 16 inputs. Neither of these numbers constitutes a full-block limit.

Complete block performance measurement is required before activation.

Before activation, the proposal requires measuring the full processing flow, delaying sponsor repairs, and charging fees for each proof that comply with transaction gas limits, including necessary overhead.

The benchmark material distinguishes between measured data for single-node and single-machine block results and model data for 16 workers. The draft requires that this evidence and the remaining performance gap be documented in the benchmark material.

An expired sponsorship may waste the builder's work, and the submitted documentation states that inclusion gas will not compensate for this effort. The specific commitment construction and encoding remain preserved within the fixed proof system specification. This proposal does not introduce any new network messages.

Disclaimer: The information on this page may have been obtained from third parties and does not necessarily reflect the views or opinions of KuCoin. This content is provided for general informational purposes only, without any representation or warranty of any kind, nor shall it be construed as financial or investment advice. KuCoin shall not be liable for any errors or omissions, or for any outcomes resulting from the use of this information. Investments in digital assets can be risky. Please carefully evaluate the risks of a product and your risk tolerance based on your own financial circumstances. For more information, please refer to our Terms of Use and Risk Disclosure.