Signed record

f82ab624dd456845a72fed0f4105b54e7013ddea7f33897ccdca5f745dab58fb

Profiles · 14 Oct 2026, 13:13 · answered by Röbel / Müritz · source ws://strfry:7777
signer npub17ll8pvqwjttlr06m7rweq8k89mstyp6yjgpsr2ssuylveq7jnxtqem0kxk
Verified in your browser
validEvent id = sha256 of its canonical serializationderived f82ab624dd456845…
validBIP-340 Schnorr signature over the idsigner npub17ll8pvqwjtt…
The record, verbatim
{
  "id": "f82ab624dd456845a72fed0f4105b54e7013ddea7f33897ccdca5f745dab58fb",
  "pubkey": "f7fe70b00e92d7f1bf5bf0dd901ec72ee0b20744920301aa10e13ecc83d29996",
  "kind": 0,
  "created_at": 1791983630,
  "content": "{\"name\":\"athiele\"}",
  "tags": [],
  "sig": "7d2a57acdbbe32e6864e568ec086efb3a57ea3b16de59ae80675bc7339624e567f5ddc1b411c665a72622fb733770c20b1321a549a9b96b133d98f9d9a7e15fb",
  "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.