Bitcoin Forum
December 06, 2016, 12:20:43 PM *
News: Latest stable version of Bitcoin Core: 0.13.1  [Torrent].
 
   Home   Help Search Donate Login Register  
Pages: [1]
  Print  
Author Topic: Significance of port 8333?  (Read 2054 times)
Andreas Schildbach
Hero Member
*****
Offline Offline

Activity: 563



View Profile WWW
January 23, 2011, 02:29:26 PM
 #1

I have Bitcoin (GUI version) running (and mining) on two machines, but can obviously only forward port 8333 to one of those.

What implications does this have for the machine without incoming connections?

Will it be able to "find" coins while mining?

Will it be able to receive coins by transactions (more precisely: will received coins be displayed without my intervention)?

Both clients are at the top of the block chain and have connections displayed in the status bar.

Will the answers be any different for "bitcoind"?

Best regards,

Andreas

Bitcoin Wallet for Android: Your own Bitcoins, in your own pocket!
https://play.google.com/store/apps/details?id=de.schildbach.wallet
1481026843
Hero Member
*
Offline Offline

Posts: 1481026843

View Profile Personal Message (Offline)

Ignore
1481026843
Reply with quote  #2

1481026843
Report to moderator
1481026843
Hero Member
*
Offline Offline

Posts: 1481026843

View Profile Personal Message (Offline)

Ignore
1481026843
Reply with quote  #2

1481026843
Report to moderator
1481026843
Hero Member
*
Offline Offline

Posts: 1481026843

View Profile Personal Message (Offline)

Ignore
1481026843
Reply with quote  #2

1481026843
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1481026843
Hero Member
*
Offline Offline

Posts: 1481026843

View Profile Personal Message (Offline)

Ignore
1481026843
Reply with quote  #2

1481026843
Report to moderator
Gavin Andresen
Legendary
*
Offline Offline

Activity: 1652


Chief Scientist


View Profile WWW
January 23, 2011, 02:47:19 PM
 #2

I have Bitcoin (GUI version) running (and mining) on two machines, but can obviously only forward port 8333 to one of those.
What implications does this have for the machine without incoming connections?

It will have only 8 (outgoing) connections.

With fewer connections, it will notice new blocks a tiny bit more slowly than the other machine, and blocks it finds will propagate to the rest of the network slightly more slowly than the other machine.  So it will spend a teeny-tiny bit more time working on an out-of-date block chain, and will be a teeny-tiny bit more likely to lose "announce a new block" races.  But I bet the effects are so small you'd never notice them.

Quote
Will it be able to "find" coins while mining?
Will it be able to receive coins by transactions (more precisely: will received coins be displayed without my intervention)?
Will the answers be any different for "bitcoind"?

Yes and yes and no.

How often do you get the chance to work on a potentially world-changing project?
SmokeTooMuch
Legendary
*
Offline Offline

Activity: 873


View Profile
January 23, 2011, 03:19:49 PM
 #3

Quote from: gavinandresen
Quote from: Goonie
Will it be able to receive coins by transactions (more precisely: will received coins be displayed without my intervention)?
yes
afaik only when "non-ip"-transactions are made (using bitcoin addresses).
if you send money to a specific ip, the client which the port is forwarded to will receive the coins.
(IP-payments are disabled by default (and will be removed in future versions afaik), so this isn't a big concern)

Date Registered: 2009-12-10 | I'm using GPG, pm me for my public key. | Bitcoin on Reddit: https://www.reddit.com/r/btc
You like what I'm doing? Why don't you send me a coin: 17Pj8jpUgY6qTaKgiopL5U48zxU4rTrkuB
bfever
Jr. Member
*
Offline Offline

Activity: 39


View Profile WWW
January 24, 2011, 09:38:17 PM
 #4

It will have only 8 (outgoing) connections.

With fewer connections, it will notice new blocks a tiny bit more slowly than the other machine, and blocks it finds will propagate to the rest of the network slightly more slowly than the other machine.  So it will spend a teeny-tiny bit more time working on an out-of-date block chain, and will be a teeny-tiny bit more likely to lose "announce a new block" races.  But I bet the effects are so small you'd never notice them.

Can't you eliminate this effect by starting Bitcoin on the second machine (not getting the port forwarding requests) with the -addnode=<ip of other machine> parameter ?
In that way, this second machine will have 7 connections to the outside world and 1 to the other machine probably being connected to a lot of more nodes.
I think even using the -connect=<ip of other machine> on the second machine is enough as the connection between the two machines is probably 1000x faster and less laggy then the internet connection to other nodes.


Use your freedom, use bitcoins !

Bitcoin Relational Database (in MySQL) aka The BiRD now available.
Universal Bitcoin Smartcard coming soon.

UBiCard - BiRD donations: 1UbicardpLQiAhGfEWKaV5xnKkmgzj1Ce
Flow
Newbie
*
Offline Offline

Activity: 17


View Profile
February 12, 2011, 02:37:43 PM
 #5

I have Bitcoin (GUI version) running (and mining) on two machines, but can obviously only forward port 8333 to one of those.

Is it not possible to forward two ports for bitcoin? E.g. 8333 and 8334 and announce this ports in the distributed database, like bittorrent does?

Flow
theymos
Administrator
Legendary
*
Offline Offline

Activity: 2492


View Profile
February 12, 2011, 07:47:56 PM
 #6

Is it not possible to forward two ports for bitcoin? E.g. 8333 and 8334 and announce this ports in the distributed database, like bittorrent does?

No. You could modify the source to use a different port, but "stock" Bitcoin greatly prefers to connect to peers on port 8333, so it wouldn't do any good.

1NXYoJ5xU91Jp83XfVMHwwTUyZFK64BoAD
MoonShadow
Legendary
*
Offline Offline

Activity: 1666



View Profile
February 12, 2011, 09:02:41 PM
 #7

Couldn't you just force the second one to connect to the other via localhost, and benefit from the first one's connections?

"The powers of financial capitalism had another far-reaching aim, nothing less than to create a world system of financial control in private hands able to dominate the political system of each country and the economy of the world as a whole. This system was to be controlled in a feudalist fashion by the central banks of the world acting in concert, by secret agreements arrived at in frequent meetings and conferences. The apex of the systems was to be the Bank for International Settlements in Basel, Switzerland, a private bank owned and controlled by the world's central banks which were themselves private corporations. Each central bank...sought to dominate its government by its ability to control Treasury loans, to manipulate foreign exchanges, to influence the level of economic activity in the country, and to influence cooperative politicians by subsequent economic rewards in the business world."

- Carroll Quigley, CFR member, mentor to Bill Clinton, from 'Tragedy And Hope'
carp
Member
**
Offline Offline

Activity: 82


View Profile
February 12, 2011, 09:31:09 PM
 #8

Is it not possible to forward two ports for bitcoin? E.g. 8333 and 8334 and announce this ports in the distributed database, like bittorrent does?

No. You could modify the source to use a different port, but "stock" Bitcoin greatly prefers to connect to peers on port 8333, so it wouldn't do any good.

of course, I was thinking about why this is a bad thing, all that I can come up with was to draw parallels to how tor is built.... able to specify bridge nodes, and specific IPs that you are allowed to talk on... and SSL options even chosen to try and minimize the detectability of what is going on.

Though, since bitcoin can use a tor proxy, it gets all those features. How well would it work to use a tor location hidden service as your available IP? If the client just forwards everything through the proxy, letting it do DNS lookups, then it would mean that you just wont resolve for any clients not using a tor proxy, but it should be transparent for anyone doing it.

Of course, if nodes are only advertised by IP (havn't looked at that, might have to soon) that wont work.
theymos
Administrator
Legendary
*
Offline Offline

Activity: 2492


View Profile
February 12, 2011, 09:57:02 PM
 #9

Though, since bitcoin can use a tor proxy, it gets all those features. How well would it work to use a tor location hidden service as your available IP? If the client just forwards everything through the proxy, letting it do DNS lookups, then it would mean that you just wont resolve for any clients not using a tor proxy, but it should be transparent for anyone doing it.

Bitcoin doesn't handle hostnames. You need to use Tor's MapAddress to use a hidden service (explicitly with -addnode), though this does work.

1NXYoJ5xU91Jp83XfVMHwwTUyZFK64BoAD
Pages: [1]
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!