From 32b577eb32218ceef00a0ccfcfcff15a402f3286 Mon Sep 17 00:00:00 2001 From: Jimmy Debe <91767824+jimstir@users.noreply.github.com> Date: Thu, 15 Feb 2024 14:55:52 -0500 Subject: [PATCH] Update peer-exchange.md --- standards/core/peer-exchange.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/standards/core/peer-exchange.md b/standards/core/peer-exchange.md index e199ed6..7b77f3e 100644 --- a/standards/core/peer-exchange.md +++ b/standards/core/peer-exchange.md @@ -34,7 +34,7 @@ As Figure 1 illustrates, the requesting node sends a request to a peer, which ac The responder replies with a list of ENRs as specified in [WAKU2-ENR](../enr.md). The [multiaddresses](https://docs.libp2p.io/concepts/addressing/) used to connect to the respective peers can be extracted from the ENRs. -![Figure 1: The responder provides a list of ENRs to the requester. These ENRs contain the information necessary for connecting to the respective peers.](./images/protocol.svg) +![Figure 1: The responder provides a list of ENRs to the requester. These ENRs contain the information necessary for connecting to the respective peers.](../../images/protocol.svg) In order to protect its anonymity, the responder MUST NOT provide peers from its actively used peer list as this opens pathways to *Neighbourhood Surveillance* attacks, as described in the [Security/Privacy Considerations Section](#securityprivacy-considerations).