nostr/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2024-12-23 00:45:53 -05:00
Code Issues Actions Packages Projects Releases Wiki Activity

doc: actions table

Browse Source
This commit is contained in:
Vlad Stan 2023-04-10 13:09:35 +03:00 committed by GitHub
parent d4324ca13a
commit cc504c1d99
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 8 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
704.md
View File

@ -45,9 +45,14 @@ If Alice wants to build he <code>dm parent key</code> for Bob then she has to:
</ul>
</details>
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/<action>/index`.
`dmpk/<action>/index`
| Action Name | Value | Path | Derive keys for |
|-----------------------|--------|---------------------|-----------------------------------|
| receive | `0` | `dmpk/0/<index>` | receiving `direct messages` |
| send | `1` | `dmpk/1/<index>` | sending `direct messages` |
| republish | `2` | `dmpk/2/<index>` | sending `republish events` |
| `draft` :market-order | `4500` | `dmpk/4500/<index>` | 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`.