Signed record

e3b587869c5c8f6ab8ae0dedf9cc6731428bf37a8cf1545cbe5f1d0806349511

Profiles · 23 Sept 2026, 13:19 · answered by Röbel / Müritz · source ws://strfry:7777
signer npub1apa2t88rcu7yrqrtku87smz2jlw5tv0kck5uemk0ej520dx9yhus34ghh3
Verified in your browser
validEvent id = sha256 of its canonical serializationderived e3b587869c5c8f6a…
validBIP-340 Schnorr signature over the idsigner npub1apa2t88rcu7…
The record, verbatim
{
  "id": "e3b587869c5c8f6ab8ae0dedf9cc6731428bf37a8cf1545cbe5f1d0806349511",
  "pubkey": "e87aa59ce3c73c41806bb70fe86c4a97dd45b1f6c5a9cceecfcca8a7b4c525f9",
  "kind": 0,
  "created_at": 1790169572,
  "content": "{\"name\":\"Kai\"}",
  "tags": [],
  "sig": "b6d91211bffeec83a9295698be17a22efcb08d03f372ee3e84e11e7237312b7b8109cf0b77b0d6adea3ae6dd80197746174d4aac8bba995b71d2db9c42ad0f21",
  "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.