From 0b9dd49f478d23802003a1344706e3e9acb9357f Mon Sep 17 00:00:00 2001
From: Oskar Thoren <ot@oskarthoren.com>
Date: Mon, 26 Aug 2019 16:28:59 +0200
Subject: [PATCH] P2P Overlay section

---
 status-spec.md | 19 +++++++++++++++++++
 1 file changed, 19 insertions(+)

diff --git a/status-spec.md b/status-spec.md
index fbed392..21297af 100644
--- a/status-spec.md
+++ b/status-spec.md
@@ -22,6 +22,25 @@ in a command line client <sup>2</sup> and a mobile app <sup>3</sup>.
 This document consists of two parts. The first outlines the specifications that
 have to be implemented in order to be a full Status client.
 
+## P2P Overlay
+
+Status clients run on the public Ethereum network, as specified by the devP2P
+network protocols. devP2P provides a protocol for node discovery which is in
+draft mode
+(here)[https://github.com/ethereum/devp2p/blob/master/discv5/discv5.md]. See
+more on node discovery and management in the next section.
+
+To communicate between Ethereum nodes, the (RLPx Transport
+Protocol, v5)[https://github.com/ethereum/devp2p/blob/master/rlpx.md] is used, which
+allows for TCP-based communication between nodes.
+
+## Node discovery and roles
+
+- Bootstrap nodes
+- Whisper relayers
+- Mailservers
+- Mobile nodes (Status Clients)
+
 ## Design Rationale
 
 ## Footnotes