diff options
| author | hodlbod <jstaab@protonmail.com> | 2024-11-17 08:05:20 -0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-11-17 08:05:20 -0800 |
| commit | ac60e1d6628164e6af262aec93c311cbef7d8063 (patch) | |
| tree | dfeb2536c84eb53e296166059a5f256be6562bef | |
| parent | 8794be6775a6264a82ed8044b14f3c5e4eb01122 (diff) | |
| parent | 108b6314299f71540190a7abf37074787fa6d698 (diff) | |
Merge pull request #1583 from s3-odara/patch-1
"user matadata"
| -rw-r--r-- | 05.md | 2 |
1 files changed, 1 insertions, 1 deletions
| @@ -10,7 +10,7 @@ On events of kind `0` (`user metadata`) one can specify the key `"nip05"` with a | |||
| 10 | 10 | ||
| 11 | Upon seeing that, the client splits the identifier into `<local-part>` and `<domain>` and use these values to make a GET request to `https://<domain>/.well-known/nostr.json?name=<local-part>`. | 11 | Upon seeing that, the client splits the identifier into `<local-part>` and `<domain>` and use these values to make a GET request to `https://<domain>/.well-known/nostr.json?name=<local-part>`. |
| 12 | 12 | ||
| 13 | The result should be a JSON document object with a key `"names"` that should then be a mapping of names to hex formatted public keys. If the public key for the given `<name>` matches the `pubkey` from the `user's metadata` event, the client then concludes that the given pubkey can indeed be referenced by its identifier. | 13 | The result should be a JSON document object with a key `"names"` that should then be a mapping of names to hex formatted public keys. If the public key for the given `<name>` matches the `pubkey` from the `user metadata` event, the client then concludes that the given pubkey can indeed be referenced by its identifier. |
| 14 | 14 | ||
| 15 | ### Example | 15 | ### Example |
| 16 | 16 | ||