I run a Bitcoin daemon on my LAN server that is connected to the Internet, and would like to use one or more Bitcoin wallets on local workstations that would connect only to my daemon. This initially works (connect=IP in wallet's bitcoin.conf), but when the daemon reaches the maxconnections, local wallets can't connect until the daemon is restarted so all the existing connections are closed.

Is there a way to permit local clients to connect to the daemon regardless of maxconnections parameter, or to somehow reserve few "slots" to particular local IP addresses?



1 Answer 1


Bitcoin Core allows you to bind a separate listening socket with specific white listing properties. It has enhanced transaction relaying for use as a gateway and an immunity to banning for bad behavior.

       Bind to given address and whitelist peers connecting to it. Use
       [host]:port notation for IPv6

This command can be used in conjunction with whiteconnections to reserve some of the maxconnections limit for connections to the whitelist socket. maxconnections=128 and whiteconnections=4 will use 8 for outgoing connections, allow a maximum of 116 incoming connections, and reserve 4 additional connections for incoming clients on the whitelisted port.

In this case you would bind the whitelist socket to an internal port, and then point LAN nodes to it. This is also useful for attaching axillary programs like P2Pool or the Bitcoin Relay Network.

  • This works perfectly, thank you very much! :)
    – SBurina
    Jul 15, 2015 at 8:36
  • As of 0.12.0 whiteconnections is not required. A non-whitelisted peer will be disconnected if a whitelisted peer attempts to connect and the node is full. Mar 9, 2016 at 13:08

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.