Ethereum developer submits EIP draft for native post-quantum signatures in frame transactions

iconKuCoinFlash
Share
AI summary iconSummary
On November 18 (UTC+8), Ethereum developer ilitteri submitted a draft EIP proposing the integration of leanSPHINCS, a hash-based post-quantum digital signature scheme, into frame transactions under EIP-8141. The draft describes a method in which digital signatures are declared via verification frames—separate from the transaction body but included in blocks—with verification occurring at the node level before execution. Developer tooling for this system has not yet been finalized, as the proposal remains in draft form without an official EIP number.

ME News reports that on November 18 (UTC+8), Ethereum developer ilitteri submitted a draft EIP proposing the introduction of the hash-based post-quantum signature scheme leanSPHINCS for frame transactions defined by EIP-8141. According to the draft, transactions specify the required signature through a dedicated verification frame; the signature data is separated from the transaction body but propagates with the transaction through the mempool and is included together in blocks, to be verified by each node prior to execution. The proposal remains in draft stage and has not yet been assigned a formal EIP number; the full technical specification is still pending completion. (Source: Foresight News)

Disclaimer: The information on this page may have been obtained from third parties and does not necessarily reflect the views or opinions of KuCoin. This content is provided for general informational purposes only, without any representation or warranty of any kind, nor shall it be construed as financial or investment advice. KuCoin shall not be liable for any errors or omissions, or for any outcomes resulting from the use of this information. Investments in digital assets can be risky. Please carefully evaluate the risks of a product and your risk tolerance based on your own financial circumstances. For more information, please refer to our Terms of Use and Risk Disclosure.