Signed record

e51292809078396bb16b8bf8c7a3931e0532abd5e477e91d4ecd57d11a0094f5

Posts · 28 Jul 2026, 15:06 · answered by Röbel / Müritz · source ws://strfry:7777
signer npub1fk70tqgmja3pyc3mwhmh3ca7gpry86e0yq9mhzkga0m0gmlv4s9qzx8ku9
Verified in your browser
validEvent id = sha256 of its canonical serializationderived e51292809078396b…
validBIP-340 Schnorr signature over the idsigner npub1fk70tqgmja3…
The record, verbatim
{
  "id": "e51292809078396bb16b8bf8c7a3931e0532abd5e477e91d4ecd57d11a0094f5",
  "pubkey": "4dbcf5811b976212623b75f778e3be404643eb2f200bbb8ac8ebf6f46fecac0a",
  "kind": 1,
  "created_at": 1785251170,
  "content": "Test 02",
  "tags": [],
  "sig": "2e778cce72e30e5cd5747609a932ba63eb05bb0a6fb84bfa8203c4561c9ff667502c14303234e8c16170e4dad371263b9b5ec66012e83936a23dca70d5668f36",
  "node_id": "roebel",
  "source": "ws://strfry:7777"
}

Anyone can re-run this check offline: serialize [0, pubkey, created_at, kind, tags, content], sha256 it, compare to the id, then verify the Schnorr signature. No Atlas required — that is what makes it a proof rather than a claim.