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 <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`.