Signed record

c9a135b698338fb2233833e386d0cf2918238600d48a44a76dac22d9184c0c23

Profiles · 25 Aug 2026, 19:48 · answered by Röbel / Müritz · source ws://strfry:7777
signer npub1ngdcwetrm8u8l0yldw0qmk6jwe5e8xa2yw0vcvk9w8c7fc9tme8q5fel68
Verified in your browser
validEvent id = sha256 of its canonical serializationderived c9a135b698338fb2…
validBIP-340 Schnorr signature over the idsigner npub1ngdcwetrm8u…
The record, verbatim
{
  "id": "c9a135b698338fb2233833e386d0cf2918238600d48a44a76dac22d9184c0c23",
  "pubkey": "9a1b876563d9f87fbc9f6b9e0ddb527669939baa239ecc32c571f1e4e0abde4e",
  "kind": 0,
  "created_at": 1787687293,
  "content": "{\"name\":\"monikar\"}",
  "tags": [],
  "sig": "f43a80e1dac3376e105c112bceea41b37651a2948f3bb2b96e1e43ed86bd802b3025c3fa0374d82c8946b6bac3060d573805d3bcf39d1948fc44c404464ac37c",
  "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.