Ethereum forum weighs leanSPHINCS frames and paid-work records
Ethereum Magicians are discussing two drafts: one for leanSPHINCS verification in EIP-8141 transactions and another to link ERC-8004 feedback to escrow-settled work.
Two Ethereum Magicians proposals put cryptographic verification and DAO work accounting on the same protocol-development docket. The “Dependency frames for leanSPHINCS signatures” draft targets EIP-8141 frame transactions; “Evaluated Work Records” proposes a record for tasks whose outcomes can be checked against escrow logs.
Both discussions were active on Nov. 19, 2026, according to the Ethereum Magicians forum. These are drafts — proposed interfaces, not deployed changes.
The leanSPHINCS draft gives EIP-8141 frame transactions native leanSPHINCS signatures through a dependency verification frame. The mechanism is narrow: “A transaction declares the signatures it depends on in a dependency verification frame. The frame executes no code. Its data is a list of (scheme, data_hash, verification_key_hash) triples, and leanSPHINCS is the only scheme.”
Size is the whole point. The draft puts a leanSPHINCS signature at 7,740 bytes, which is why the frame design matters: the dependency is declared in a dedicated frame rather than handled as ordinary executable code.
This proposal lands after earlier work on Ethereum’s post-quantum direction. Coinvote, reporting from Decrypt and CoinDesk, says EIP-8288 was published in June as a draft standard co-authored by Ethereum co-founder Vitalik Buterin and developer Thomas Coratger. That same report says Buterin’s position on leanPCS shifted from skepticism to optimism on Nov. 16, while June SPHINCS- research included input from Ethereum Foundation cryptographers.
Coinvote reports that unmodified standalone quantum-safe signature verification on Ethereum currently requires about 150,000 gas, and that a future leanSPHINCS verification under protocol-level aggregation would cost about 3,000 gas — a 50-fold reduction by the published figures. The proposal does not say that this draft has achieved the 3,000-gas figure; those remain Coinvote’s current and projected numbers, not a measurement of the dependency frame itself.
The same report says quantum-resistant user signatures can expand from 65 bytes to between 1 and 6 kilobytes, and zero-knowledge proofs can rise from a few hundred bytes to roughly 128 kilobytes, with the batching approach bundling large cryptographic elements before transactions hit the base layer.
The second proposal starts from a gap in ERC-8004 feedback entries. As the Ethereum Magicians draft puts it: “An ERC-8004 feedback entry can name a task, but nothing ties its score to paid work. This draft posts one entry per escrow-settled task, with evidence checkable against the escrow’s logs.”
Its proposed unit is an evaluated work record — one entry per escrow-settled task. The ERC also proposes an outcome mapping for ERC-8183 jobs, placing payment settlement, task outcome, and feedback into one record flow while building on ERC-8004 feedback entries.
The draft’s reference code includes a writer and reader with no dependencies, plus test vectors from real tasks, according to the forum post. The Ethereum Magicians draft lists five test vectors from BrainChain mainnet (chain 274663) and three from BrainChain testnet, for eight total.
The proposal sits beside ERC-8466, “Agent Credit History,” and ERC-8458, “Agent Income Statements.” In the desk’s assessment, that positioning could make the record relevant to DAO operators and agents evaluating performance across systems, though the proposal leaves several interface questions open.
Reviewers asked whether the profile should define an on-chain view so a contract can check one task’s outcome without reading a full record. Others questioned whether ERC-8004 metadata is the right place for an agent to declare which escrow workers are its own, and whether readers pinning each escrow’s deployer-published descriptor is sufficient or whether the profile should name a registry of descriptors. The draft does not settle any of them. The draft does not establish adoption beyond the BrainChain test vectors listed in its reference material.
The concrete exposure is in the two drafts themselves: EIP-8141 implementers would need to assess the proposed dependency-frame interface and its 7,740-byte signature payload, and systems using ERC-8004 or ERC-8183 would need to decide whether escrow-settled outcomes should become portable records. Neither the leanSPHINCS frames draft nor the Evaluated Work Records draft is presented as an accepted Ethereum standard, and the interface questions raised by reviewers remain unresolved in both. ETH$1,777.45▲0.49% is the network token underlying both proposals.