From 65a44195fb6952afc9c8a0e706a9008448091ccc Mon Sep 17 00:00:00 2001 From: Vlad Stan Date: Mon, 10 Apr 2023 13:25:15 +0300 Subject: [PATCH] doc: send/receive keys --- 704.md | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/704.md b/704.md index c7ba9ca..5fca835 100644 --- a/704.md +++ b/704.md @@ -49,12 +49,14 @@ We notate the above derived `direct message public key` with `dmpk`. Then we ca | Action Name | Value | Path | Derive keys for | |-----------------------|--------|---------------------|-----------------------------------| -| **receive** | `0` | `dmpk/0/` | receiving `direct messages` | -| **send** | `1` | `dmpk/1/` | sending `direct messages` | +| **send** | `0` | `dmpk/0/` | sending `direct messages` | +| **receive** | `1` | `dmpk/1/` | receiving `direct messages` | | `draft`: republish | `2` | `dmpk/2/` | sending `republish events` | -| `draft` :market-order | `4500` | `dmpk/4500/` | sending NIP45 `market orders` | +| `draft`: market-order | `4500` | `dmpk/4500/` | sending NIP45 `market orders` | - send, receive, marketplace +The client (creator of the `dmpk`) must: + - use a new send key (`dmpk/0/`) for each event it signs. It starts from `0` and increments after an event is signed. + - create filters for the public keys it expects to receive messages to (`dmpk/1/`). It is recommended to listen for the next `10` keys. ## Exchange the `direct message parent key` If `Alice` wants to signal `Bob` that she is ready to use this NIP (for more privacy) she must: