TBNGovernanceCrypto
A hash-only rollup: OP Stack L2 accounts as Lamport-style hash chains, no ECDSA inside the L2
Publication: Ethereum Research - Latest topics
Author: Hadamard
Source published: 24/10/2026, 23:24:10 UTC
Briefing created: 24/10/2026, 23:48:19 UTC
Based on a feed excerpt; full article content has not been acquired. Source evidence retrieved 24/10/2026, 23:28:25 UTC.
Briefings
This briefing describes a proposed OP Stack L2 architecture where transactions use hash chains instead of signatures, eliminating ECDSA reliance. The system uses keccak-256 hash chains to bind spending to preimages, with a commit-reveal mechanism ensuring only the first valid reveal can spend. It supports one-time addresses, bridged tokens, and gas-free transactions, though it lacks a full sequencer and relies on external trust assumptions. The design aims to provide post-quantum payment security on Ethereum L2s while maintaining compatibility with existing Ethereum protocols.
Key points
- The system runs on Ethereum mainnet (chain ID 42069000) with L2 transactions carrying no signatures, using only keccak-256 preimage resistance as the cryptographic assumption.
- A commit-reveal step binds each preimage to a transaction before the preimage becomes public, preventing attackers from spending the same preimage with different transactions.
Context
The proposal outlines a novel OP Stack L2 design for post-quantum payments on Ethereum L2s, replacing ECDSA signatures with hash chains. It supports one-time addresses, bridged tokens, and gas-free transactions, though it lacks a full sequencer and relies on external trust assumptions.
Limitations
Evidence is limited to a single author's draft post; no independent verification or peer review is provided. The system lacks a full sequencer and relies on external trust assumptions. The design is untested in production and has not been built yet.
Generated by Bittrees-hosted qwen35-2b sha256:aaf42c8b7c3c on 24/10/2026, 23:48:19 UTC. Based on publisher-provided feed evidence; may not cover the full original article. Check the source for details.
View archived briefing on IPFS
bafybeig5mhx77m4hvjqgnhdbdqday7yjncv6f7covytjxk57tthxhnef2a