GovernanceCrypto

Inventory of PQ P2P Migrations in the Consensus Layer

Read full article at source ↗

Based on a feed excerpt; full article content has not been acquired. Source evidence retrieved 27/10/2026, 07:28:25 UTC.

Briefings

A 2026 inventory identifies that Ethereum's consensus-layer networking lacks a post-quantum migration profile, leaving ENRs, Discovery v5, and QUIC/TLS vulnerable. The current spec uses secp256k1 signatures (64 bytes) and ECDH key exchange, which are insufficient against quantum threats. Key exchange risks decryption if classical agreements break, while signatures require quantum capability for forgery. The article maps required changes without selecting a specific algorithm, noting that lattice-based schemes like ML-DSA are de facto candidates due to size constraints, though none are ready for deployment.

Key points

• Ethereum consensus-layer networking currently lacks a post-quantum migration profile, leaving ENRs, Discovery v5, and QUIC/TLS vulnerable to quantum threats.
• Current secp256k1 signatures (64 bytes) and ECDH key exchange are insufficient; lattice-based schemes like ML-DSA are de facto candidates due to size constraints but not yet deployed.

Context

This inventory maps required cryptographic changes for Ethereum CL networking over libp2p and QUIC, covering Discovery v5, ENR signatures, and QUIC/TLS key exchange. It highlights that while hash-based signatures are promoted for consensus, the P2P layer's size limits make lattice-based schemes the practical standard candidates for networking, though no specific algorithm or rollout date is selected.

Limitations

Coverage is limited to Ethereum CL networking over libp2p and QUIC; the Execution Layer and TCP/Noise fallback are excluded. The article does not select a specific PQ signature, KEM, fork, or rollout date, and does not provide activation schedules or algorithm recommendations.

Generated by Bittrees-hosted qwen35-2b sha256:aaf42c8b7c3c on 27/10/2026, 07:30:55 UTC. Based on publisher-provided feed evidence; may not cover the full original article. Check the source for details.

View archived briefing on IPFS
bafybeifhrxrx2oxrsnkh2ofjyf3altyenfy3vghkqqu4wqeqq6qa3cdjpa