Add EIP: Dependency frames for leanSPHINCS signatures

This thread is for discussing a new draft EIP:

Summary

The EIP gives EIP-8141 frame transactions native leanSPHINCS signatures through a dependency verification frame, the interface EIP-8288 aggregates.

  • 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.
  • The signature is not part of the transaction. It travels beside it in the mempool and in the block, and every node verifies it natively before execution.
  • Accounts read their dependencies with FRAMEPARAM and FRAMEDATACOPY and approve on them.

Why

A leanSPHINCS signature is 7,740 bytes. The lasting answer to that size is aggregation: one proof per block in place of each signature. Proving is not ready for every block yet, but post-quantum accounts need the interface aggregation will keep from the start, because an account’s validation code fixes where it looks for a signature.

This EIP fixes that interface. A later upgrade replaces the block’s signatures with one aggregate proof, as EIP-8288 does, and adds other dependency kinds, such as proofs, without changing transactions or accounts. The frame is the only declaration of a signature, so nothing is stated twice.

Status

The draft has the abstract and the motivation. The specification is in progress.

2 Likes