From 0ca9be82247d9c1f93ac4319042d2364b7d18b30 Mon Sep 17 00:00:00 2001 From: fiatjaf Date: Thu, 29 Dec 2022 21:02:32 -0300 Subject: clarify nip19 purpose. --- 19.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) (limited to '19.md') diff --git a/19.md b/19.md index 8f05b67..b9973cf 100644 --- a/19.md +++ b/19.md @@ -6,7 +6,9 @@ bech32-encoded entities `draft` `optional` `author:jb55` `author:fiatjaf` `author:Semisol` -This NIP specifies all bech32-encoded entities. +This NIP standardizes bech32-formatted strings that can be used to display keys, ids and other information in clients. These formats are not meant to be used anywhere in the core protocol, they are only meant for displaying to users, copy-pasting, sharing, rendering QR codes and inputting data. + +It is recommended that ids and keys are stored in either hex or binary format, since these formats are closer to what must actually be used the core protocol. ## Bare keys and ids @@ -50,3 +52,7 @@ These possible standardized `TLV` types are indicated here: - pubkey: `3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d` - relay: `wss://r.x.com` - relay: `wss://djbas.sadkb.com` + +## Notes + +- `npub` keys MUST NOT be used in NIP-01 events or in NIP-05 JSON responses, only the hex format is supported there. -- cgit v1.2.3