Signed record
37181384132d9e1857378e700fd13b5d9e84d756bf1935ad581422a68605db10
Profiles · 14 Oct 2026, 13:01 · answered by Röbel / Müritz · source ws://strfry:7777
signer npub13yrprkym3uf6gw3ypclsk2pe3j3ve4rut8vkt0tkdv2mlne4ex3sh8pkqp
signer npub13yrprkym3uf6gw3ypclsk2pe3j3ve4rut8vkt0tkdv2mlne4ex3sh8pkqp
Verified in your browser
validEvent id = sha256 of its canonical serializationderived 37181384132d9e18…
validBIP-340 Schnorr signature over the idsigner npub13yrprkym3uf…
The record, verbatim
{
"id": "37181384132d9e1857378e700fd13b5d9e84d756bf1935ad581422a68605db10",
"pubkey": "890611d89b8f13a43a240e3f0b28398ca2ccd47c59d965bd766b15bfcf35c9a3",
"kind": 0,
"created_at": 1791982860,
"content": "{\"name\":\"u_peter\"}",
"tags": [],
"sig": "c2ab1cb7c03ed3d477909f4b0beba236837429c22ebade3598016501899dd66889ade61ca7518cda4fb071dcd97adf92562cc98241be0237c7a151ba9af6eef5",
"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.