Note: Passing these checks confirms the keys are linked and the signatures are valid — it does not mean the identity is post-quantum secure. The Bitcoin timestamp check relies on a public block explorer rather than running a full Bitcoin node, so a compromised explorer could fool it.

You can check a post-quantum key-link event two ways: look it up on a relay by pubkey, or paste the event JSON directly. The event you're checking (kind 9999) wraps a public announcement (kind 1) and carries a Bitcoin timestamp proof. Verification checks each piece separately and reports the results below: both Nostr signatures, the link between the two events, each post-quantum signature (ML-DSA-44, ML-DSA-65, SLH-DSA-128s, Falcon-512 — ML-KEM-768 is for encryption, so it has no signature to check), that all required algorithms are present, that the event really belongs to the claimed identity, and the Bitcoin timestamp.

Back to preparation page