Try a token

An emem:fact token names one record by the BLAKE3-256 hash of its bytes, and says which cell it is about. Your browser asks emem.dev for those bytes with one GET, hashes them itself, decodes them and compares the cell. Nothing is written.

CHECK THIS TOKEN

Or try: the real token same name, another cell (M4) one character changed (M7)

What this page checks, and what it does not

• L0 hash: the bytes emem.dev returns hash to the name in the token. A changed byte gives another name.
• L1 cell: the record's own cell equals the cell in the token. The right record cited for another place is refused.
• Not here: the record carries no signature of its own. The operator signs a Merkle root over BLAKE3 hashes of a batch of records, and the batch sits in a public log. VIEW THE DEMO checks both for the Keylong record. The source is named, not hashed, so checking it means re-reading it (L3: the demo shows the saved source window, and its live option re-reads the pixel).

The same token on emem.dev's own checker, which also verifies the server's signed resolve receipt: emem.dev/verify?q=<token>. On a phone its result starts below the first screen.