What would need to appear on-chain if proofs were aggregated before submission? In a report published on November 16, 2026, Foresight News said Vitalik Buterin had described EIP-8288 as a way to aggregate STARK proofs in the mempool, leaving a claim hash and a main proof to be submitted on-chain rather than every underlying signature or proof. This is a proposal, not a reported change to Ethereum’s current transaction records.
According to the report, Buterin said he had recently shifted from skepticism to optimism about leanPCS. He compared three approaches: leanSPHINCS, a specific quantum-safe signature scheme; leanSTARK, a general-purpose proof system that requires a defined instruction set; and leanPCS, a polynomial commitment scheme. He said leanPCS would require only a specified field, such as a 128-bit binary field, and could therefore reach similar generality sooner.
From an EVM perspective, Buterin put STARK verification using leanPCS at roughly 20,000–40,000 gas. He suggested that it could bring a broader shift toward cryptographic proofs closer, with leanSTARK added later. Those figures and expectations are his account of the approach, not measurements of an enacted deployment.
Source: foresightnews.pro (originally published 2026-11-16 15:52 UTC+8)