Signed record

a81d6b01ada88b7c67825f9f67795308015e1680b998bc4fd7fdb03d64d56c55

Profiles · 23 Sept 2026, 04:22 · answered by Röbel / Müritz · source ws://strfry:7777
signer npub1mj4tttgpclwqvwvk8ve30ysu46hwwhd8w3mqfn4dg59le00xrwsqa6scdp
Verified in your browser
validEvent id = sha256 of its canonical serializationderived a81d6b01ada88b7c…
validBIP-340 Schnorr signature over the idsigner npub1mj4tttgpclw…
The record, verbatim
{
  "id": "a81d6b01ada88b7c67825f9f67795308015e1680b998bc4fd7fdb03d64d56c55",
  "pubkey": "dcaab5ad01c7dc0639963b3317921caeaee75da7747604cead450bfcbde61ba0",
  "kind": 0,
  "created_at": 1790137342,
  "content": "{\"name\":\"sascha_jochens\"}",
  "tags": [],
  "sig": "fd348f8ed32cc04845fec64b128988ce0a4330be51205b38dbeb4e31bc3a62a03f3b21c77721a6d0acbcb1fef2b3dabf6b3d36298ab26be9d5fb482f7b93ad42",
  "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.