From fc07e08c589e8719f48d2bd72a8dc2e664229e89 Mon Sep 17 00:00:00 2001 From: kaichaosun Date: Fri, 26 Jan 2024 14:22:07 +0800 Subject: [PATCH] max length of digests. --- content/docs/rfcs/67/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/docs/rfcs/67/README.md b/content/docs/rfcs/67/README.md index bbc16546..16a2acaf 100644 --- a/content/docs/rfcs/67/README.md +++ b/content/docs/rfcs/67/README.md @@ -18,7 +18,7 @@ Waku nodes can query messages by given an array of message hash. This is useful ## Request The parameters are the following: -* `digests`: array of unique identifiers of the messages that request node is interested in, refer to [Deterministic Message Hashing](/spec/14/#deterministic-message-hashing). +* `digests`: array of unique identifiers of the messages that request node is interested in, refer to [Deterministic Message Hashing](/spec/14/#deterministic-message-hashing). The max length of `digests` should be 20. ```proto message QueryWakuMessagesRequest { @@ -29,7 +29,7 @@ message QueryWakuMessagesRequest { ## Response The response are the following: -* `messages`: array of messages that the response node has, refer to [Waku Message](/spec/14). The order of the response messages is not ensured to be the same as the order of the request digests. And the response messages could be less than `digests`, which means the response node don't have the messages corresponding to specific digests. +* `messages`: array of messages that the response node has, refer to [Waku Message](/spec/14). The order of the response messages is not ensured to be the same as the order of the request digests. And the response messages could be less than `digests`, which means the response node don't have the messages corresponding to specific digests. The request node needs to recalculate the message hash to match digest with a WakuMessage in `messages`. ```proto message QueryWakuMessagesResponse {