From 4c663d3db085664fb7c63bb89df4106f9beb36b6 Mon Sep 17 00:00:00 2001 From: harsh jain Date: Fri, 3 Nov 2023 12:48:31 +0700 Subject: [PATCH] Update content/docs/rfcs/34/README.md Co-authored-by: Hanno Cornelius <68783915+jm-clius@users.noreply.github.com> --- content/docs/rfcs/34/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/docs/rfcs/34/README.md b/content/docs/rfcs/34/README.md index 93707833..0e7da70e 100644 --- a/content/docs/rfcs/34/README.md +++ b/content/docs/rfcs/34/README.md @@ -51,7 +51,7 @@ To save bandwidth, and as a trade off to anonymity, responders MAY maintain a larger cache of exchange peers and randomly sample response sets from this local cache. This local cache SHOULD store peers by `cluster_id`/`shard` for faster retrieval. For peers without shard info, the cache can maintain a separate set of peers. -The size of each `cluster_id`/`shard` pair being maintained in cache SHOULD be large enough to allow randomly sampling peer sets that (on average) do not overlap too much. +The size of the cache for each `cluster_id`/`shard` pair SHOULD be large enough to allow randomly sampling peer sets that (on average) do not overlap too much. The responder SHOULD periodically replace the oldest peers in the cache. This document provides recommended choices for the cache size in the [Implementation Suggestions Section](#implementation-suggestions).