A big reason is that the two ways are almost the same, so it makes sense to choose one instead of supporting both.
The HTTP approach has two advantages over the DNS approach:
1. it's easier to add other metadata to the pubkeys, like we do today in some cases;
2. it's 10000x easier to support dynamic name resolution, for providers that have multiple users, each with its own name and pubkey.
The first NIP-05 draft used DNS records, but then I realized that it was inferior.
fiatjaf /
npub180…jh6w6
2024-07-15 18:16:19
in reply to nevent1q…dxfu
Author Public Key
npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6Published at
2024-07-15 18:16:19Event JSON
{
"id": "7bce87324be527cb25956d94d567a6110bff4fb43519426f7a0f95170cc2267f",
"pubkey": "3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d",
"created_at": 1721060179,
"kind": 1,
"tags": [
[
"client",
"gossip"
],
[
"p",
"d0debf9fb12def81f43d7c69429bb784812ac1e4d2d53a202db6aac7ea4b466c"
],
[
"p",
"b7ed68b062de6b4a12e51fd5285c1e1e0ed0e5128cda93ab11b4150b55ed32fc"
],
[
"e",
"28afdfde1f4fa17506f17fb65ee0e8691d1fc5b96e95864bd63a4ac81d8de1f3",
"wss://nos.lol/",
"root"
],
[
"e",
"83223258ba79383a20a85a55a4d5fb157175227a22bc41f120c86048e62021ec",
"wss://bouncer.nostree.me/",
"reply"
]
],
"content": "A big reason is that the two ways are almost the same, so it makes sense to choose one instead of supporting both.\n\nThe HTTP approach has two advantages over the DNS approach:\n1. it's easier to add other metadata to the pubkeys, like we do today in some cases;\n2. it's 10000x easier to support dynamic name resolution, for providers that have multiple users, each with its own name and pubkey.\n\nThe first NIP-05 draft used DNS records, but then I realized that it was inferior.",
"sig": "7897256bf4bad6ae4f82d4b5835499ecfb2078155c249e95977c26457cc721d2cb1c8379d2094fbf4e24a4602fbd6346d2f3a18e065769adbad91d6f99e758ae"
}