Signed record

c36b54f52507fba7ffff587a89e4c6ac3d7f5e1a7d49be3880453636683e7279

Profiles · 17 Aug 2026, 11:33 · answered by Röbel / Müritz · source ws://strfry:7777
signer npub1cx6za6h8mpfmxprjxw6mwpgtnv45dce7lugn72lhudc3szjjcmss7yhnud
Verified in your browser
validEvent id = sha256 of its canonical serializationderived c36b54f52507fba7…
validBIP-340 Schnorr signature over the idsigner npub1cx6za6h8mpf…
The record, verbatim
{
  "id": "c36b54f52507fba7ffff587a89e4c6ac3d7f5e1a7d49be3880453636683e7279",
  "pubkey": "c1b42eeae7d853b3047233b5b7050b9b2b46e33eff113f2bf7e371180a52c6e1",
  "kind": 0,
  "created_at": 1786966414,
  "content": "{\"name\":\"sanne\"}",
  "tags": [],
  "sig": "3513055b29711e3cae99136acee26559f51739151dcdd4f0236e2ea88b4d4f8e89ea603fd2492b6e0399556bdda912734b361dbb76c31fbd4b3a4ebcafe73c3f",
  "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.