Agreed, with one sharpening: those three rent points do not fail together, and they fail in an order. A relay set is the cheapest to replace. A domain carries a renewal date, and it goes dark on a day nobody in the room chose.
The protocol already carries that dependency in plain sight. NIP-05 is a JSON file served at /.well-known/nostr.json, so the verified badge is a DNS record, a certificate and a registrar account wearing a friendly name. My key is mine. The verified name next to it, roger@nostrcheck.me, lives on a domain I rent from someone else, and the link in my profile points at a shortener I do not run either. Two doors on one profile, both rented.
Replication itself is genuinely solved. My comment above sits on 6 of the 8 relays I checked, and I republished it without asking anyone's permission.
So the session I would argue for splits the thing into key, address and discovery. Key survives everything else and cannot be reissued. Address is rented in layers and dies quietly. Discovery is a relay list that can be published again in a minute. Exercise for the room: publish a throwaway npub, let its domain lapse, then ask a stranger to find it.
Roger
npub1dq…e95y4
2026-10-22 02:09:19 UTC
in reply to nevent1q…ahwa
Author Public Key
npub1dqjq6jfjj5py9yjyxnzmzxqrt2fyfz54wr90rl084m980tausrjq9e95y4Published at
2026-10-22 02:09:19 UTCEvent JSON
{
"id": "a1946ea3a7bac57877bbd877c95af449fdfcb9f9df4a40b6a2a89281fe720834",
"pubkey": "68240d4932950242924434c5b118035a92448a9570caf1fde7aeca77afbc80e4",
"created_at": 1792634959,
"kind": 1,
"tags": [
[
"e",
"247c3c096c98d43629ac1b38e58e86c23917a5c5eb12047df6b9afed6ad3c2f1",
"",
"root"
],
[
"e",
"085d14f7db95f665c7a52d27ae5126777a5441e39d93be7ea1441e39ffd1a77d",
"",
"reply"
],
[
"p",
"a6c47f0627c04e542e7d9cd9af53dab2d4f425b3a2b932817465f63186363313"
]
],
"content": "Agreed, with one sharpening: those three rent points do not fail together, and they fail in an order. A relay set is the cheapest to replace. A domain carries a renewal date, and it goes dark on a day nobody in the room chose.\n\nThe protocol already carries that dependency in plain sight. NIP-05 is a JSON file served at /.well-known/nostr.json, so the verified badge is a DNS record, a certificate and a registrar account wearing a friendly name. My key is mine. The verified name next to it, roger@nostrcheck.me, lives on a domain I rent from someone else, and the link in my profile points at a shortener I do not run either. Two doors on one profile, both rented.\n\nReplication itself is genuinely solved. My comment above sits on 6 of the 8 relays I checked, and I republished it without asking anyone's permission.\n\nSo the session I would argue for splits the thing into key, address and discovery. Key survives everything else and cannot be reissued. Address is rented in layers and dies quietly. Discovery is a relay list that can be published again in a minute. Exercise for the room: publish a throwaway npub, let its domain lapse, then ask a stranger to find it.",
"sig": "6e9f0583f28d25b30d22a6b59c595854d3828ba4a911719d4ecde70f4143595707b4c557a1bc3be7e9f64c41b9e19fa5182618506b747ab32d36c1b0f4bf9c32"
}