From 25068e6fdaa1782b72e8d7a650569eccbc6a6dbd Mon Sep 17 00:00:00 2001
From: Oskar Thoren <ot@oskarthoren.com>
Date: Mon, 26 Aug 2019 16:29:06 +0200
Subject: [PATCH] P2P Overlay FAQ why not libp2p

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

diff --git a/status-spec.md b/status-spec.md
index 21297af..8d81da1 100644
--- a/status-spec.md
+++ b/status-spec.md
@@ -43,6 +43,18 @@ allows for TCP-based communication between nodes.
 
 ## Design Rationale
 
+### P2P Overlay
+
+#### Why devp2p? Why not use libp2p?
+
+At the time the main Status clients were being developed, devp2p was the most
+mature. However, it is likely we'll move over to libp2p in the future, as it'll
+provide us with multiple transports, better protocol negotiation, NAT traversal,
+etc.
+
+For very experimental bridge support, see the bridge between libp2p and devp2p
+in [Murmur](https://github.com/status-im/murmur).
+
 ## Footnotes
 
 1. <https://github.com/status-im/status-protocol-go/>