diff options
| -rw-r--r-- | 19.md | 2 |
1 files changed, 1 insertions, 1 deletions
| @@ -22,7 +22,7 @@ These are the possible bech32 prefixes: | |||
| 22 | 22 | ||
| 23 | Example: the hex public key `3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d` translates to `npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6`. | 23 | Example: the hex public key `3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d` translates to `npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6`. |
| 24 | 24 | ||
| 25 | The bech32 encodings of keys and ids are not meant to be used inside the standard NIP-01 event formats or inside the filters, they're meant for human-friendlier display and input only. Clients should still accept keys in both hex and npubformat for now, and convert internally. | 25 | The bech32 encodings of keys and ids are not meant to be used inside the standard NIP-01 event formats or inside the filters, they're meant for human-friendlier display and input only. Clients should still accept keys in both hex and npub format for now, and convert internally. |
| 26 | 26 | ||
| 27 | ## Shareable identifiers with extra metadata | 27 | ## Shareable identifiers with extra metadata |
| 28 | 28 | ||