From c766f8892b46b26a91ac1e570cb605a8074b78b2 Mon Sep 17 00:00:00 2001 From: ekzyis Date: Thu, 18 Jan 2024 23:32:36 +0100 Subject: [PATCH 1/4] NIP-47: fix typo --- 47.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/47.md b/47.md index c6540d51..4916658c 100644 --- a/47.md +++ b/47.md @@ -17,7 +17,7 @@ This NIP describes a way for clients to access a remote Lightning wallet through * **wallet service**: Nostr app that typically runs on an always-on computer (eg. in the cloud or on a Raspberry Pi). This app has access to the APIs of the wallets it serves. ## Theory of Operation - 1. **Users** who which to use this NIP to send lightning payments to other nostr users must first acquire a special "connection" URI from their NIP-47 compliant wallet application. The wallet application may provide this URI using a QR screen, or a pasteable string, or some other means. + 1. **Users** who wish to use this NIP to send lightning payments to other nostr users must first acquire a special "connection" URI from their NIP-47 compliant wallet application. The wallet application may provide this URI using a QR screen, or a pasteable string, or some other means. 2. The **user** should then copy this URI into their **client(s)** by pasting, or scanning the QR, etc. The **client(s)** should save this URI and use it later whenever the **user** makes a payment. The **client** should then request an `info` (13194) event from the relay(s) specified in the URI. The **wallet service** will have sent that event to those relays earlier, and the relays will hold it as a replaceable event. From d0812229a5569372a6cd1bdb8d148beb1820585d Mon Sep 17 00:00:00 2001 From: fiatjaf Date: Sun, 21 Jan 2024 16:08:45 -0300 Subject: [PATCH 2/4] use jsonc in some places. --- 01.md | 11 +++++------ 52.md | 4 ++-- 72.md | 10 +++++----- 3 files changed, 12 insertions(+), 13 deletions(-) diff --git a/01.md b/01.md index 80ee7924..46316ea5 100644 --- a/01.md +++ b/01.md @@ -14,7 +14,7 @@ Each user has a keypair. Signatures, public key, and encodings are done accordin The only object type that exists is the `event`, which has the following format on the wire: -```json +```jsonc { "id": <32-bytes lowercase hex-encoded sha256 of the serialized event data>, "pubkey": <32-bytes lowercase hex-encoded public key of the event creator>, @@ -22,7 +22,7 @@ The only object type that exists is the `event`, which has the following format "kind": , "tags": [ [...], - ... + // ... ], "content": , "sig": <64-bytes lowercase hex of the signature of the sha256 hash of the serialized event data, which is the same as the "id" field> @@ -58,17 +58,16 @@ To prevent implementation differences from creating a different event ID for the Each tag is an array of strings of arbitrary size, with some conventions around them. Take a look at the example below: -```json +```jsonc { - ..., "tags": [ ["e", "5c83da77af1dec6d7289834998ad7aafbd9e2191396d75ec3cc27f5a77226f36", "wss://nostr.example.com"], ["p", "f7234bd4c1394dda46d09f35bd384dd30cc552ad5541990f98844fb06676e9ca"], ["a", "30023:f7234bd4c1394dda46d09f35bd384dd30cc552ad5541990f98844fb06676e9ca:abcd", "wss://nostr.example.com"], ["alt", "reply"], - ... + // ... ], - ... + // ... } ``` diff --git a/52.md b/52.md index 5ac116b9..f35d9040 100644 --- a/52.md +++ b/52.md @@ -38,7 +38,7 @@ The list of tags are as follows: The following tags are deprecated: * `name` name of the calendar event. Use only if `title` is not available. -```json +```jsonc { "id": <32-bytes lowercase hex-encoded SHA-256 of the the serialized event data>, "pubkey": <32-bytes lowercase hex-encoded public key of the event creator>, @@ -99,7 +99,7 @@ The list of tags are as follows: The following tags are deprecated: * `name` name of the calendar event. Use only if `title` is not available. -```json +```jsonc { "id": <32-bytes lowercase hex-encoded SHA-256 of the the serialized event data>, "pubkey": <32-bytes lowercase hex-encoded public key of the event creator>, diff --git a/72.md b/72.md index c0fffffc..4bafce06 100644 --- a/72.md +++ b/72.md @@ -12,7 +12,7 @@ The goal of this NIP is to create moderator-approved public communities around a `kind:34550` SHOULD include any field that helps define the community and the set of moderators. `relay` tags MAY be used to describe the preferred relay to download requests and approvals. -```json +```jsonc { "created_at": , "kind": 34550, @@ -42,14 +42,14 @@ The goal of this NIP is to create moderator-approved public communities around a Any Nostr event can be submitted to a community by anyone for approval. Clients MUST add the community's `a` tag to the new post event in order to be presented for the moderator's approval. -```json +```jsonc { "kind": 1, "tags": [ ["a", "34550::", ""], ], "content": "hello world", - ... + // ... } ``` @@ -59,7 +59,7 @@ Community management clients MAY filter all mentions to a given `kind:34550` eve The post-approval event MUST include `a` tags of the communities the moderator is posting into (one or more), the `e` tag of the post and `p` tag of the author of the post (for approval notifications). The event SHOULD also include the stringified `post request` event inside the `.content` ([NIP-18-style](18.md)) and a `k` tag with the original post's event kind to allow filtering of approved posts by kind. -```json +```jsonc { "pubkey": "<32-bytes lowercase hex-encoded public key of the event creator>", "kind": 4550, @@ -70,7 +70,7 @@ The post-approval event MUST include `a` tags of the communities the moderator i ["k", ""] ], "content": "", - ... + // ... } ``` From 363e4958cf10fc35f3168ca51374da06c0e5b2ee Mon Sep 17 00:00:00 2001 From: Asai Toshiya Date: Tue, 23 Jan 2024 13:09:10 +0900 Subject: [PATCH 3/4] Add kinds for NIP-15 --- README.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/README.md b/README.md index cf3827e8..91179cd7 100644 --- a/README.md +++ b/README.md @@ -94,6 +94,8 @@ They exist to document what may be implemented by [Nostr](https://github.com/nos | `42` | Channel Message | [28](28.md) | | `43` | Channel Hide Message | [28](28.md) | | `44` | Channel Mute User | [28](28.md) | +| `1021` | Bid | [15](15.md) | +| `1022` | Bid confirmation | [15](15.md) | | `1040` | OpenTimestamps | [03](03.md) | | `1063` | File Metadata | [94](94.md) | | `1311` | Live Chat Message | [53](53.md) | @@ -136,6 +138,8 @@ They exist to document what may be implemented by [Nostr](https://github.com/nos | `30015` | Interest sets | [51](51.md) | | `30017` | Create or update a stall | [15](15.md) | | `30018` | Create or update a product | [15](15.md) | +| `30019` | Marketplace UI/UX | [15](15.md) | +| `30020` | Product sold as an auction | [15](15.md) | | `30023` | Long-form Content | [23](23.md) | | `30024` | Draft Long-form Content | [23](23.md) | | `30030` | Emoji sets | [51](51.md) | From 6dd003508567dd780f3d8da12f0f9a62449cb992 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ioan=20Biz=C4=83u?= Date: Tue, 23 Jan 2024 18:36:38 +0200 Subject: [PATCH 4/4] #p refers to pubkeys, *not* "event pubkeys". --- 01.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/01.md b/01.md index 46316ea5..c1e37480 100644 --- a/01.md +++ b/01.md @@ -124,7 +124,7 @@ Clients can send 3 types of messages, which must be JSON arrays, according to th "ids": , "authors": , "kinds": , - "#": , + "#": , "since": , "until": , "limit":