From cc504c1d9986b728fb7712b2623ccd39ab6a77d1 Mon Sep 17 00:00:00 2001 From: Vlad Stan Date: Mon, 10 Apr 2023 13:09:35 +0300 Subject: [PATCH] doc: actions table --- 704.md | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/704.md b/704.md index 2723517..ce3db5a 100644 --- a/704.md +++ b/704.md @@ -45,9 +45,14 @@ If Alice wants to build he dm parent key for Bob then she has to: -We notate the above derived `direct message public key` with `dmpk`. +We notate the above derived `direct message public key` with `dmpk`. Then we can define paths of the form `dmpk//index`. -`dmpk//index` +| Action Name | Value | Path | Derive keys for | +|-----------------------|--------|---------------------|-----------------------------------| +| receive | `0` | `dmpk/0/` | receiving `direct messages` | +| send | `1` | `dmpk/1/` | sending `direct messages` | +| republish | `2` | `dmpk/2/` | sending `republish events` | +| `draft` :market-order | `4500` | `dmpk/4500/` | sending NIP45 `market orders` | send, receive, marketplace @@ -76,4 +81,4 @@ If `Alice` wants to signal `Bob` that she is ready to use this NIP (for more pri > **Note** the reason for using `sha256(shared_secret)` for the `d` tag is so that outside observers do not even know that `Alice` and `Bob` have started to communicate. Any other value for the `d` tag would reveal that the message is intended for `Bob.` - After both `Alice` and `Bob` have published the `kind: 35709` event, they can start to publish and listen to events using the `one-use-keys`. + After both `Alice` and `Bob` have both published the `kind: 35709` event, they can start to publish and listen to events using the `one-use-keys`.