<p>Yes and no.  Don't use 8332 for your custom client's communication port, that is the default rpcport.</p>

<p>You can run an arbitrary number of bitcoind instances on your machine, as long as they are given different -port= and -rpcport= arguments, and they can all communicate with each other (using -addnode=127.0.0.1:...port... or -connect=127.0.0.1:...port... ).</p>

CC BY-SA 3.0
2011-11-04T15:49:25.193Z
2011-11-04T15:49:25.193Z
gavinandresen
<p>I`m currently programming some TCP communication in my custom Bitcoin client. I am wondering if it is possible for the official client to communicate with it if they are sitting on the same machine? For example, if I'd send a version message to localhost:8333 claiming my return address is localhost:8332, will the standard client respond as if it was communicating with a node on the internet?</p>

<protocol><testing><tcp>
Can a Bitcoin node send messages to a program on the same machine?
ThePiachu
# Can a Bitcoin node send messages to a program on the same machine?

(Asked by: username_0 on 2011-10-30)

I`m currently programming some TCP communication in my custom Bitcoin client. I am wondering if it is possible for the official client to communicate with it if they are sitting on the same machine? For example, if I'd send a version message to localhost:8333 claiming my return address is localhost:8332, will the standard client respond as if it was communicating with a node on the internet?

**Tags:** protocol, testing, tcp


---

## 1 answers

### Answer by username_1 on 2011-11-04. Score: 3 | Accepted answer

Yes and no. Don't use 8332 for your custom client's communication port, that is the default rpcport.

You can run an arbitrary number of bitcoind instances on your machine, as long as they are given different -port= and -rpcport= arguments, and they can all communicate with each other (using -addnode=127.0.0.1:...port... or -connect=127.0.0.1:...port... ).


---

