It is not enough to just make up a TLD, who is going to run that TLD? What happens when they censor you just like existing DNS can? How to stop spam and sybil?
All these questions are exactly what pkarr.nuh.dev was made to answer.
1. Bittorrent DHT is how you maintain ultimate censorship resistance
2. If you don't keep republishing your DNS-like record it gets dropped by the nature of the DHT, so that solves spam and Sybil
3. Your relay/hosting provider(s) who you already pay for keeping your data, periodically refresh your records on the DHT
Most importantly I tested all of that and showed that a small server can keep up to 100k users records alive on the DHT with >95% availability
Once you add aggressive caching, it is a solved problem.
But it will demand switching to ed25519 as the root identity
Nuh 🔻
npub1jvx…7yqz
2023-08-08 09:36:01
in reply to nevent1q…r7ra
Author Public Key
npub1jvxvaufrwtwj79s90n79fuxmm9pntk94rd8zwderdvqv4dcclnvs9s7yqzPublished at
2023-08-08 09:36:01Event JSON
{
"id": "ec93dc2314bcb1f28cee24026bcb929bfc3812aedea6ab3cd44bb29ce2c5a9e7",
"pubkey": "930ccef12372dd2f16057cfc54f0dbd94335d8b51b4e2737236b00cab718fcd9",
"created_at": 1691480161,
"kind": 1,
"tags": [
[
"e",
"aeceeae26e3ac2068eeab68692e263e823a97944e0a74915f62e6a80e0749b5c",
"wss://offchain.pub",
"root"
],
[
"p",
"5e336907a3dda5cd58f11d162d8a4c9388f9cfb2f8dc4b469c8151e379c63bc9"
]
],
"content": "It is not enough to just make up a TLD, who is going to run that TLD? What happens when they censor you just like existing DNS can? How to stop spam and sybil?\n\nAll these questions are exactly what pkarr.nuh.dev was made to answer.\n\n1. Bittorrent DHT is how you maintain ultimate censorship resistance \n2. If you don't keep republishing your DNS-like record it gets dropped by the nature of the DHT, so that solves spam and Sybil \n3. Your relay/hosting provider(s) who you already pay for keeping your data, periodically refresh your records on the DHT\n\nMost importantly I tested all of that and showed that a small server can keep up to 100k users records alive on the DHT with \u003e95% availability \n\nOnce you add aggressive caching, it is a solved problem.\n\nBut it will demand switching to ed25519 as the root identity",
"sig": "6b5ffc245c595e8d8073df3089c8add1dfd466e8ae24c7f35439b84d4369b1d8c5bb8ff718054ac3c27f1a7d07758454798e320a190cb9e12a7359d910078883"
}