I'm writing a Bitcoin web app that is to be deployed on an external server over which I have no control. I probably won't have access to standard Bitcoin port (8333). Will this cause a problem when connecting to standard Bitcoin clients, or can they handle communicating with a non-standard port number? Are there any Bitcoin-related applications that also use other ports to communicate (like a pool or the like)?

link|improve this question

72% accept rate
In what way(s) does the web app have to interact with the Bitcoin network? Will the Bitcoin client be running on the machine running the web app? – David Schwartz Oct 7 '11 at 21:44
I intend to write my own Bitcoin client for the web app, so I hope to be able to fully interact with the Bitcoin network. Alternatively, I might want to run just a pool in the web app. So, there is no problem with client customization as long as the network can also handle that. – ThePiachu Oct 7 '11 at 22:23
feedback

1 Answer

up vote 2 down vote accepted

If you make only outbound connections it won't matter what ports you use. Your client will be able to fully participate in the network without any issues.

link|improve this answer
So, if my app can start a connection with another client stating that my address has port :80, it will receive response on port :80? – ThePiachu Oct 7 '11 at 22:31
When you connect to a client, you will receive responses on the connection you just made to that client. The Bitcoin network uses persistent TCP connections that remain active so long as both nodes continue running. – David Schwartz Oct 7 '11 at 22:33
Btw, I think you used an unnecessary "and". Can't edit your post, since I would need to change at least 6 characters ;). – ThePiachu Oct 7 '11 at 22:34
Thanks. I changed the structure of that sentence after writing it and didn't complete the change. – David Schwartz Oct 7 '11 at 22:36
feedback

Your Answer

 
or
required, but never shown

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