// signature verification
Signature Verification
All articles on this blog are signed with ML-DSA-65 (NIST FIPS 204). You can independently verify any signature here — using only the public key and the article content, without trusting this website.
Cryptographic signatures create trust without a leap of faith. Each signature binds an article to its original state — regardless of whether the CMS, server, or database is ever compromised. Since ML-DSA-65 is post-quantum secure, this guarantee remains valid even as powerful quantum computers become a reality. Verification runs entirely in your browser without contacting external servers.
Public Key (ML-DSA-65)
48904116e9d8f6f65aa54c03c32b8a1f81519744…daadaaa4c456dfc1Signed Message Format
documentId | locale | title | blocks (JSON, media = SHA-256 hashes)These four fields are concatenated with | and passed as raw UTF-8 bytes directly to ML-DSA-65 — no pre-hashing. ML-DSA processes the message internally with SHAKE-256 (FIPS 204 §5.2). Media files are embedded as SHA-256 hashes within the blocks. Title and block content are fetched automatically from Strapi — you only need to enter the document ID.