From 8d1fc60a9a6c8e749514124ec912dd1e9bc0f154 Mon Sep 17 00:00:00 2001 From: Vlad Stan Date: Mon, 10 Apr 2023 17:04:02 +0300 Subject: [PATCH] Update 704.md --- 704.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/704.md b/704.md index b181010..4184352 100644 --- a/704.md +++ b/704.md @@ -57,7 +57,7 @@ We notate the above derived `direct-message parent key` with `dmpk`. Then we ca The client (creator of the `dmpk`) must: - use a new send key (`dmpk/1/`) 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/2/`). It is recommended to listen for the next `10` keys and increment the index once a key is used (see [BIP-44 address gap logic](https://github.com/bitcoin/bips/blob/master/bip-0044.mediawiki#user-content-Address_gap_limit)). + - create filters for the public keys it expects to receive messages to (`dmpk/2/`). It is recommended to listen for the next `10` public keys and increment the index once a key is used (see [BIP-44 address gap logic](https://github.com/bitcoin/bips/blob/master/bip-0044.mediawiki#user-content-Address_gap_limit)). ## 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: