Signed record

c4a6c7818f20adbe32583a9f625968bb129c91a825ef6239869dc1a13c7619e5

Posts · 28 Jul 2026, 19:53 · answered by Röbel / Müritz · source ws://strfry:7777
signer npub1fk70tqgmja3pyc3mwhmh3ca7gpry86e0yq9mhzkga0m0gmlv4s9qzx8ku9
Verified in your browser
validEvent id = sha256 of its canonical serializationderived c4a6c7818f20adbe…
validBIP-340 Schnorr signature over the idsigner npub1fk70tqgmja3…
The record, verbatim
{
  "id": "c4a6c7818f20adbe32583a9f625968bb129c91a825ef6239869dc1a13c7619e5",
  "pubkey": "4dbcf5811b976212623b75f778e3be404643eb2f200bbb8ac8ebf6f46fecac0a",
  "kind": 1,
  "created_at": 1785268383,
  "content": "Test 04",
  "tags": [],
  "sig": "6011b83d70eab136134f15068a43c5f0198909ca16bf4d157b97a8844d8f8acad743b50c69bc05ed803cba6b0e77e17153ba211b05bbbe85eabf1bbdd2ffa283",
  "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.