From 50dafa1eff3d947db5d61d59d33938ea7f30c7d0 Mon Sep 17 00:00:00 2001 From: Yusef Napora Date: Thu, 26 Sep 2019 14:52:10 -0400 Subject: [PATCH] small clarification about topics in peering state --- pubsub/gossipsub-wip.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/pubsub/gossipsub-wip.md b/pubsub/gossipsub-wip.md index ed4ccd3..0ac8b71 100644 --- a/pubsub/gossipsub-wip.md +++ b/pubsub/gossipsub-wip.md @@ -235,9 +235,11 @@ There are three main pieces of peering state: `fanout` map contains topics to which we _are not_ subscribed. In addition to the gossipsub-specific state listed above, the libp2p pubsub -implementation maintains some "router-agnostic" state. This includes the set of +framework maintains some "router-agnostic" state. This includes the set of topics to which we are subscribed, as well as the set of topics to which each of -our peers is subscribed. +our peers is subscribed. Elsewhere in this document, we refer to +`peers.floodsub[topic]` and `peers.gossipsub[topic]` to denote floodsub or +gossipsub capable peers within a specific topic. ### Message Cache