From 691cd462675143def984b69fb9906c758d27ec10 Mon Sep 17 00:00:00 2001
From: Andreas Schildbach <andreas.schildbach@bloq.com>
Date: Sun, 17 Jul 2022 19:42:57 +0200
Subject: [PATCH] ForwardingService: limit the number of peer connections
 required

Nowadays on testnet or signet it takes a long time to discover enough bloom-enabled peers.
---
 .../src/main/java/org/bitcoinj/examples/ForwardingService.java  | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/examples/src/main/java/org/bitcoinj/examples/ForwardingService.java b/examples/src/main/java/org/bitcoinj/examples/ForwardingService.java
index 621e55d43..1a38ca67b 100644
--- a/examples/src/main/java/org/bitcoinj/examples/ForwardingService.java
+++ b/examples/src/main/java/org/bitcoinj/examples/ForwardingService.java
@@ -42,6 +42,7 @@ import static com.google.common.base.Preconditions.checkNotNull;
 public class ForwardingService {
     static final String usage = "Usage: address-to-send-back-to [mainnet|testnet|signet|regtest]";
     static final int requiredConfirmations = 1;
+    static final int MAX_CONNECTIONS = 4;
     private final BitcoinNetwork network;
     private final Address forwardingAddress;
     private final WalletAppKit kit;
@@ -118,6 +119,7 @@ public class ForwardingService {
         // Download the blockchain and wait until it's done.
         kit.startAsync();
         kit.awaitRunning();
+        kit.peerGroup().setMaxConnections(MAX_CONNECTIONS);
     }
 
     /**