Signed record

7879193a3182526b3f58bf55413bf4339bbadd54f2eab6895343517706b5f2d2

Profiles · 31 Aug 2026, 11:44 · answered by Röbel / Müritz · source ws://strfry:7777
signer npub1h5e8wn3kf24p7vsu02wu6x63fws3q3kku0ayknwz6xfz6atqy4uqn9h6p9
Verified in your browser
validEvent id = sha256 of its canonical serializationderived 7879193a3182526b…
validBIP-340 Schnorr signature over the idsigner npub1h5e8wn3kf24…
The record, verbatim
{
  "id": "7879193a3182526b3f58bf55413bf4339bbadd54f2eab6895343517706b5f2d2",
  "pubkey": "bd32774e364aaa1f321c7a9dcd1b514ba11046d6e3fa4b4dc2d1922d75602578",
  "kind": 0,
  "created_at": 1788176679,
  "content": "{\"name\":\"Birgit\"}",
  "tags": [],
  "sig": "516b033f6567525c2529b0f7aad74a50389ffffc5b3dca0d03f010ee0f68c5d69b3e8577cd1108c7bf38d568ade5848e33463ff441246d964e2a866e70958d84",
  "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.