From 68439127973adefbd8e6967fef1d846655ab23b1 Mon Sep 17 00:00:00 2001
From: Vlad Stan <stan.v.vlad@gmail.com>
Date: Mon, 10 Apr 2023 13:31:18 +0300
Subject: [PATCH] doc: add note

---
 704.md | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

diff --git a/704.md b/704.md
index 5fca835d..6771fc01 100644
--- a/704.md
+++ b/704.md
@@ -64,10 +64,12 @@ If `Alice` wants to signal `Bob` that she is ready to use this NIP (for more pri
 ```json
  {
   "key": <the direct message parent key>,
-  "send_index": <integer (optional), ...>,
-  "receive_index": <integer (optional), ...>,
+  "send_index": <integer (optional), the index of the last key used to sign an event>,
+  "receive_index": <integer (optional), the index of the last key an event was received to>,
  }
  ```
+  > **Note** `send_index` and `receive_index` are optional, but they help the client a lot in knowing what the state is. Alternatively (when an account is retored) the client would have to scan the public keys until unused ones are found.
+ 
  - publish a `Parameterized Replaceable Event` ([NIP-33](https://github.com/nostr-protocol/nips/blob/master/33.md)) having:
 
 ```json
@@ -83,4 +85,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 both 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 published the `kind: 35709` event, they can start to publish and listen to events using the `one-use-keys`.