Ethereum contributor Marchhill submitted a draft proposal to the EIP repository on November 13, 2026. The submission activates the LEANSTARK_SCHEME, a fallback scheme in EIP-8288 authored by Vitalik Buterin and Thomas Coratger. This unified draft brings together generic verification, proof identity, resource bounds, dependency digests, and batch payment schemes, superseding pull request #12654.
The original EIP-8288 focuses on aggregating cryptographic signatures and off-chain computational proofs using block-level recursive STARKs. Marchhill’s proposal specifies technical rules allowing multiple transactions to share a single proof. However, its most significant change lies in the cost-sharing framework among users, sponsors, and block builders.
One Shared Proof for 256 Transactions
The proposed mechanism enables multiple transaction claims to share the same cryptographic proof. Even though computational proofs are merged, the system keeps payments, signatures, account nonces, and receipts separated for each transaction. This separation ensures each account’s records remain independent on the Ethereum ledger.
Block builders have the flexibility to include a subset of valid claims in a block. If certain claims in an initial batch are dropped, other valid claims are still processed without requiring users to resign their transactions.
Gas Cost Breakdown and Dependency Limits
The payment scheme introduces a sponsorship mechanism that covers costs per retained batch leaf. Each leaf can hold up to 256 transaction claims, while a single proof step can handle up to 16 inputs.
Estimated gas costs are broken down across several components: 15,400 gas for native verification, 572,000 gas for regular generic verification, and 5,100 gas for the intrinsic proof portion. At the batch level, the system requires 675,000 gas for leaf payment overhead and 4,200 gas for batch claims.
The proposal also establishes resource limits via a provisional block cap of 16,384 distinct dependencies. This cap is evaluated independently of standard network gas limits, preventing proof verification from eating into regular transaction computational quotas.
Incentive Flows and Public Mempool Access
Claim discount incentives and sponsor payments will flow directly to block builders. This setup compensates builders who allocate block space to assemble and verify transaction proof batches.
The system does not discard legacy methods. Conventional standalone proofs can still operate through the public mempool, ensuring users who bypass batching can continue transacting as usual.
For users and block builders alike, the proposal strikes a balance between gas savings and execution certainty. Discussions in the EIP repository now serve as a testing ground to evaluate the readiness of this batch verification framework for deployment.
Reported by crypto.news.
Also read: How Crypto Staking Works and Its Risks
Disclaimer: This article is for informational and educational purposes only, not financial advice. Cryptocurrency assets are highly volatile and carry significant risk. Always do your own research (DYOR) and never invest more than you can afford to lose.
