From 89571ff497f7ad66275402e95bc3628a0ad197b6 Mon Sep 17 00:00:00 2001
From: "fryorcraken.eth" <git@fryorcraken.xyz>
Date: Thu, 15 Dec 2022 14:26:57 +1100
Subject: [PATCH] feat!: remove peer exchange from protocols to wait on by
 default

This is because peer exchange is still experimental and not enabled
on all prod fleets.

The issue is that we could be connected to a remote peer with relay/
filter/lightpush yet never resolve because peer exchange is missing.

This also shows the limit of this function logic which should be
addressed as we dive deeper in peer management.
---
 packages/core/src/lib/wait_for_remote_peer.ts | 3 ---
 1 file changed, 3 deletions(-)

diff --git a/packages/core/src/lib/wait_for_remote_peer.ts b/packages/core/src/lib/wait_for_remote_peer.ts
index 4e15b5d7e5..60302587f7 100644
--- a/packages/core/src/lib/wait_for_remote_peer.ts
+++ b/packages/core/src/lib/wait_for_remote_peer.ts
@@ -155,9 +155,6 @@ function getEnabledProtocols(waku: Waku): Protocols[] {
   if (waku.lightPush) {
     protocols.push(Protocols.LightPush);
   }
-  if (waku.peerExchange) {
-    protocols.push(Protocols.PeerExchange);
-  }
 
   return protocols;
 }