From 2db9908166a83642d067d473a8953a1da828c031 Mon Sep 17 00:00:00 2001 From: sandwich <299465+dskvr@users.noreply.github.com> Date: Tue, 23 Jan 2024 19:46:42 +0000 Subject: [PATCH] limitations->limitation fix, integer solution, nested obj disclaimed --- 66.md | 16 +++++++++++++--- 1 file changed, 13 insertions(+), 3 deletions(-) diff --git a/66.md b/66.md index 66da811b..dccbec9e 100644 --- a/66.md +++ b/66.md @@ -98,11 +98,21 @@ Tags should be used to represent the Relay's abilities and meta at any given poi - Boolean values from `NIP-11`, for example ``` - [ "L", "nip11.limitations" ] - [ "l", "payment_required", "nip11.limitations" ] //nip11.limitations.payment_required==true - [ "l", "auth_required", "nip11.limitations" ] //nip11.limitations.auth_required==true + [ "L", "nip11.limitation" ] + [ "l", "payment_required", "nip11.limitation" ] //nip11.limitation payment_required==true + [ "l", "auth_required", "nip11.limitation" ] //nip11.limitation auth_required==true ``` +#### NIP-11 Integer Values +Any NIP-11 values that are integers should not be included as NIP-32 labels, instead they should use the `nip11` tag. + +``` +[ "nip11", "65535", "limitation.max_message_length" ] +``` + +#### NIP-11 Nested Objects +NIP-11 nested objects are not supported by NIP-66 at this time (For example, fees) + #### Geo tags NIP-YAGT - `NIP-66` leverages a draft NIP for geo tags, see [YAGT](https://github.com/nostr-protocol/nips/pull/952) ```