From 3bc10d18f397dc7b97fff347fd493f78d890edae Mon Sep 17 00:00:00 2001 From: Josef Widder Date: Mon, 5 Dec 2022 17:39:44 +0100 Subject: [PATCH] req --- spec/p2p/p2p-top-level.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/spec/p2p/p2p-top-level.md b/spec/p2p/p2p-top-level.md index c70f7b98e..99b097d72 100644 --- a/spec/p2p/p2p-top-level.md +++ b/spec/p2p/p2p-top-level.md @@ -126,6 +126,8 @@ The question is under which conditions [[TM-REQ-CR-COMM.0]] is sufficient to imp ### Requirements on the p2p layer +There are **local requirements** that express needs as connections to neighbors + #### [TM-REQ-CR+P2P-STABLE.0] In order to make sure that we can help a peer to make progress, the p2p layer MUST ensure that we need to stay connected to that peer sufficiently long to get a good view of its state, and to act on it by sending messages. @@ -153,6 +155,9 @@ TODO: stay connected to good peers for some time TODO: New nodes can join / new validators can join +Since the systems we are building are decentralized and distributed, the global requirements can only be ensured by local actions of the distributed nodes. For instance, openness has been ensured by distinguishing inbound and outbound connections, and making sure that there are always nodes with open inbound connections. + + ## Mempool