From 9eb63db372cd2b4f5243cc20c740b6a1bc1754c1 Mon Sep 17 00:00:00 2001 From: Sasha Date: Tue, 2 Jul 2024 12:22:01 +0200 Subject: [PATCH] improve peer and connection managment section --- informational/req-res-reliability.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/informational/req-res-reliability.md b/informational/req-res-reliability.md index e1326b9..3470efb 100644 --- a/informational/req-res-reliability.md +++ b/informational/req-res-reliability.md @@ -46,9 +46,11 @@ To address this we suggest following metrics: In case a protocol failed to use any service node more than once - connection to it should be dropped and a new service node should be connected and added to the pool instead. -- During discovery of new peers it is better to filter out based on ENR / multiaddress. For example in some cases `circuit-relay` addresses are not needed when we try to find and connect to peers directly. +- During discovery of new service nodes it is better to filter out based on ENR / multiaddress. +For example in some cases `circuit-relay` addresses are not needed when we try to find and connect to service nodes directly. -- When peer is discovered second time, we need to be sure to keep connection information up to date in Peer Store. +- When a service node is discovered second time, +we need to be sure to keep connection information up to date in Peer Store. ### Light Push