Governance
Exploring post-quantum signature aggregation for EIP-8288
Publication: Ethereum Research - Latest topics
Author: manel1874
Source published: 16/11/2026, 16:33:57 UTC
Briefing created: 16/11/2026, 17:51:49 UTC
Based on a feed excerpt; full article content has not been acquired. Source evidence retrieved 16/11/2026, 16:43:26 UTC.
Briefings
This briefing reports on a study by Manuel B. Santos at MultiVM Labs exploring post-quantum signature aggregation for EIP-8288. The research tests five signature schemes (Falcon-512, ML-DSA-44, FORS, Raccoon-128, and Raccoon-G) under a STARK proof system. Key findings indicate that while Falcon, ML-DSA, and FORS fit within leanVM's commitment limits, Raccoon-G verification exceeds the 268 million witness word limit, requiring a multi-proof aggregation strategy. The study was conducted on an Apple M4 Pro with 24 GiB RAM, using median proof generation times and memory usage metrics.
Key points
- Five signature schemes (Falcon-512, ML-DSA-44, FORS, Raccoon-128, Raccoon-G) were tested under a STARK proof system to support EIP-8288's recursive aggregation.
- Raccoon-G verification exceeds leanVM's 268 million witness word limit, necessitating a multi-proof aggregation approach using five separate STARK proofs.
Context
EIP-8141 and EIP-8288 provide a path for wallets to choose signing schemes while network verification uses a common proof. The study investigates whether post-quantum schemes can be integrated into leanVM's proof system, which is critical for scalable, secure wallet implementations.
Limitations
Experimental results are based on median proof generation times and memory usage from three fresh runs on an Apple M4 Pro with 24 GiB RAM. The study covers single and batched signature verification but does not include performance data for 10, 30, 70, or 100 distinct signatures per category.
Generated by Bittrees-hosted qwen35-2b sha256:aaf42c8b7c3c on 16/11/2026, 17:51:49 UTC. Based on publisher-provided feed evidence; may not cover the full original article. Check the source for details.
View archived briefing on IPFS
bafybeialxvy4ywblfmuc2t23urp2pxcsj32gvjg7giyxgtstetmfl3c2fq