<p>If you can allocate multiple IP addresses to one machine (hint: you can), then yes, you can have one node bound to multiple IP addresses and serving peers on all of them. It's impossible to tell whether two nodes you are connected to are actually the same node so that doesn't matter. Note that doing this does not help the network any more than having one IP address and one node.</p>

CC BY-SA 3.0
2017-10-15T05:46:54.647Z
Why doesn't it help? Whats the difference between one node with 5 IPs vs 5 nodes with 1 IP each. In terms of helping spread the blockchain and signalling no 2x
masterq
CC BY-SA 3.0
2017-10-15T15:15:15.410Z
If your node goes down, all of the nodes connected to your 5 IPs lose a connection, and that could be many nodes. If there are 5 nodes and one goes down, then only the nodes connected to that one IP address lose a connection. More nodes adds more robustness to the network and is generally better.
Ava Chow
CC BY-SA 3.0
2017-10-15T15:58:42.080Z
Well I only have one server so the other option would be to host multiple VMs which could cause the same problem and I guess running one node with 100+ connections spread across 5 VMs would use more resources than having 1 node with 100 connections active. How do I bind multiple IPs to the node?
masterq
CC BY-SA 3.0
2017-10-14T21:47:21.303Z
2017-10-14T21:47:21.303Z
Ava Chow
<p>I run a full Bitcoin node on a powerful server however rather than setting up multiple I was wondering if it's possible to use multiple IP addresses on one installation and one running process? Without people being able to detect it's the same node (not easily anyway).</p>

<full-node><network>
Run a full node with multiple IP addresses
masterq
# Run a full node with multiple IP addresses

(Asked by: username_0 on 2017-10-14)

I run a full Bitcoin node on a powerful server however rather than setting up multiple I was wondering if it's possible to use multiple IP addresses on one installation and one running process? Without people being able to detect it's the same node (not easily anyway).

**Tags:** full-node, network


---

## 1 answers

### Answer by username_1 on 2017-10-14. Score: 2 | Accepted answer

If you can allocate multiple IP addresses to one machine (hint: you can), then yes, you can have one node bound to multiple IP addresses and serving peers on all of them. It's impossible to tell whether two nodes you are connected to are actually the same node so that doesn't matter. Note that doing this does not help the network any more than having one IP address and one node.

> **Comments:**
> **username_0**: Why doesn't it help? Whats the difference between one node with 5 IPs vs 5 nodes with 1 IP each. In terms of helping spread the blockchain and signalling no 2x  
> **username_1**: If your node goes down, all of the nodes connected to your 5 IPs lose a connection, and that could be many nodes. If there are 5 nodes and one goes down, then only the nodes connected to that one IP address lose a connection. More nodes adds more robustness to the network and is generally better.  
> **username_0**: Well I only have one server so the other option would be to host multiple VMs which could cause the same problem and I guess running one node with 100+ connections spread across 5 VMs would use more resources than having 1 node with 100 connections active. How do I bind multiple IPs to the node?  

---

