Digital Currency

Add as a preferred source on Google

Ethereum Draft Would Add leanSPHINCS Checks to Frame Transactions

The proposal ties the check to EIP-8141 and keeps signature data outside the transaction itself.

Updated 1 min read
A developer tests transaction-signing code at a laptop in Zug, Switzerland. / TokenPost.ai (mono)
A developer tests transaction-signing code at a laptop in Zug, Switzerland. / TokenPost.ai (mono)

PR #12672 proposes that EIP-8141 transactions use a dependency verification frame to declare leanSPHINCS checks, giving nodes a rule to apply before execution of each covered transaction.

The dependency verification frame would identify the required check. Nodes would verify a separate signature payload before execution; that payload would stay apart from the transaction as it moved through the mempool and into a block.

The EIP-8288 proposal describes an aggregation design that could use the same verification interface and reserves leanSTARK for future use. That draft cites the bandwidth and gas demands of quantum-resistant signatures and proofs as reasons to aggregate checks.

The pull request’s full specification remains pending; it has no assigned EIP number, remains marked Draft and has not been merged.

Related articles

View all