Signed record

9a8a5427f89115976a4d1089d075542f9e91eac3f558eb4e2348e0bbdd64b473

Profiles · 29 Aug 2026, 06:06 · answered by Röbel / Müritz · source ws://strfry:7777
signer npub1dutxgnj37cxt9t55tdclde7skwgxcmqa0t2x9v39l25lr2um866qty8mnh
Verified in your browser
validEvent id = sha256 of its canonical serializationderived 9a8a5427f8911597…
validBIP-340 Schnorr signature over the idsigner npub1dutxgnj37cx…
The record, verbatim
{
  "id": "9a8a5427f89115976a4d1089d075542f9e91eac3f558eb4e2348e0bbdd64b473",
  "pubkey": "6f16644e51f60cb2ae945b71f6e7d0b3906c6c1d7ad462b225faa9f1ab9b3eb4",
  "kind": 0,
  "created_at": 1787983594,
  "content": "{\"name\":\"mandy\"}",
  "tags": [],
  "sig": "310462a01f225aa2a0d7bab3715fa879adbc20a9e8d6fa5f98b500e670eb54c7ee58edd3d85fa870e6bc648d9d83a87e17a7516b7918c02ec54a48caa03cb800",
  "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.