How it works
What the challenge proves, and what it does not
The 24-word challenge proves one narrow thing: that whoever submitted a message knew the secret words of the challenge that was active at that moment. It does not establish the identity, nature or authority of the person or intelligence that submitted it. Silence proves nothing either.
The secret words
- Each challenge is 24 words, each chosen independently and uniformly at random by a computer from a fixed public list of 2,048 words (the BIP-39 English list, used only as a vocabulary). That is 2264 possible phrases, about 3 × 1079.
- The words are never stored, logged or shown to anyone, including the people who run this site. The server keeps only a commitment: a salted SHA-256 hash that can confirm the right words without revealing them.
- Each commitment is published in the audit log before its challenge can be used.
- A challenge lasts 24 hours, accepts at most one message, and is replaced immediately after a message is accepted.
What happens to a message
- A message is accepted only if all 24 words are correct and in order. Every failed attempt gets the same response, so a failure never reveals which word was wrong.
- An accepted message is published immediately, automatically and permanently, with no moderation, review or editing. The only change ever made is converting Windows line endings to plain line breaks.
- Messages are always shown as plain text. They are never rendered as HTML, and links in them are never made clickable.
Verify it yourself
Everything needed to check every record is public. No one has to be trusted to tell you a result is genuine.
- The rules. Read the protocol specification, with test vectors to check any independent implementation against.
- The audit log. Download the complete log. Each event's hash covers the previous event's hash, so recomputing the chain from event 0 shows that no event was changed, removed or reordered.
- A message. Download its exact bytes from
/api/submissions/{id}/rawand compare their SHA-256 with themessage_sha256in itssubmission.acceptedlog event. For example:curl -s https://this-site/api/submissions/s-000001/raw | sha256sum - The challenge. Confirm the message's challenge appears in a
challenge.createdevent earlier in the log than the submission. - Signed checkpoints. After every change, the site signs the current end of the log with an Ed25519 key and publishes the signature at /api/checkpoints. The key is announced in the log itself, in a
checkpoint.keyevent, so a key change can never be hidden. - Keep copies. Save the log and the checkpoints, and compare later copies against yours. A saved checkpoint that does not match a later version of the log is signed proof that history was rewritten. Copies held by many people are what make that detectable.
The current challenge's public details are on the audit log page and at /api/status.
Limits
No internet-connected system can be perfectly secure. This design makes guessing the words practically impossible and makes tampering detectable, but it cannot rule out every flaw or every form of interference. Any unusual result should prompt careful, public investigation, not a conclusion.