Signed record

a67e1427a604fb0938c4cbceff63fba3e927b2acf5c178a7eb396c80a1c48e8a

Profiles · 1 Sept 2026, 05:24 · answered by Röbel / Müritz · source ws://strfry:7777
signer npub1yd32tsk90jc4dsgw5z80kxkpn3c3n0pvgxzk6ermf0jse67rwjeq0yzzd6
Verified in your browser
validEvent id = sha256 of its canonical serializationderived a67e1427a604fb09…
validBIP-340 Schnorr signature over the idsigner npub1yd32tsk90jc…
The record, verbatim
{
  "id": "a67e1427a604fb0938c4cbceff63fba3e927b2acf5c178a7eb396c80a1c48e8a",
  "pubkey": "2362a5c2c57cb156c10ea08efb1ac19c7119bc2c41856d647b4be50cebc374b2",
  "kind": 0,
  "created_at": 1788240251,
  "content": "{\"name\":\"sebastian_michels\"}",
  "tags": [],
  "sig": "067705264ff0cb6decf4725c05c2e97267d7c66764326c11e88786c4d225c3e4bb5b16e8af918a27cddae18092884f5472cd1b24fa3a380756c1ce0969fda236",
  "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.