Rendered at 13:48:43 GMT+0000 (Coordinated Universal Time) with Cloudflare Workers.
Retr0id 6 hours ago [-]
> Does it mean Merkle’s authentication tree is still used today?
> It is. In fact, the Merkle tree is a fundamental part of blockchain.
True, and merkle trees are just about everywhere, but more interestingly it's part of SLH-DSA (the NIST standardization of SPHINCS+), a quantum-secure signature scheme. And it's not just any old merkle tree, it's a continued evolution of the original Lamport signature scheme discussed in the article.
> Current signature schemes can use as few as 32 bytes per key and 64 bytes per signature [RFC8032], but post-quantum replacements are much larger. [...] a new form of X.509 certificate that integrates logging with certificate issuance [...] This achieves the following: Log entries do not scale with public key and signature sizes. Entries replace public keys with hashes and do not contain signatures
> It is. In fact, the Merkle tree is a fundamental part of blockchain.
True, and merkle trees are just about everywhere, but more interestingly it's part of SLH-DSA (the NIST standardization of SPHINCS+), a quantum-secure signature scheme. And it's not just any old merkle tree, it's a continued evolution of the original Lamport signature scheme discussed in the article.
> Current signature schemes can use as few as 32 bytes per key and 64 bytes per signature [RFC8032], but post-quantum replacements are much larger. [...] a new form of X.509 certificate that integrates logging with certificate issuance [...] This achieves the following: Log entries do not scale with public key and signature sizes. Entries replace public keys with hashes and do not contain signatures