Bitcoin Forum
September 28, 2016, 05:05:32 PM *
News: Due to DDoS attacks, there may be periodic downtime.
 
   Home   Help Search Donate Login Register  
Pages: [1]
  Print  
Author Topic: Simple to implement feature requests  (Read 2070 times)
BlueSky
Newbie
*
Offline Offline

Activity: 8


View Profile
February 08, 2010, 09:00:02 AM
 #1

First request:
Optional connect to IP dialog.

Explanation:
BitCoin connects to the network(of peers) by getting one of a number of IP's from IRC at present, once connected to a single peer other connections can be made, so if only 1 IP on the list are available then you can connect to the network & make connections to other IP's(this is my assumption, please correct me if I am wrong).

This is somewhat similar to how Tor works, when you first start it up it attempts to connect to a public list of IP's(public bridge nodes). This list being public is accessible to organisations that want to prevent the use of Tor(for example the Chinese or Iranian government). And so as a consequence these IP's are blocked, and you cannot connect from these countries.

However there is the option to connect to the ip of a bridge (if you know one, a friend in a free country running Tor in bridge mode perhaps) and so this circumvents regime blocking attempts and is very robust.

Adding this feature will allow Bitcoin to function despite regime efforts to prevent it.
1475082332
Hero Member
*
Offline Offline

Posts: 1475082332

View Profile Personal Message (Offline)

Ignore
1475082332
Reply with quote  #2

1475082332
Report to moderator
1475082332
Hero Member
*
Offline Offline

Posts: 1475082332

View Profile Personal Message (Offline)

Ignore
1475082332
Reply with quote  #2

1475082332
Report to moderator
1475082332
Hero Member
*
Offline Offline

Posts: 1475082332

View Profile Personal Message (Offline)

Ignore
1475082332
Reply with quote  #2

1475082332
Report to moderator
"This isn't the kind of software where we can leave so many unresolved bugs that we need a tracker for them." -- Satoshi
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1475082332
Hero Member
*
Offline Offline

Posts: 1475082332

View Profile Personal Message (Offline)

Ignore
1475082332
Reply with quote  #2

1475082332
Report to moderator
1475082332
Hero Member
*
Offline Offline

Posts: 1475082332

View Profile Personal Message (Offline)

Ignore
1475082332
Reply with quote  #2

1475082332
Report to moderator
satoshi
Founder
Sr. Member
*
Offline Offline

Activity: 364


View Profile
February 08, 2010, 04:37:24 PM
 #2

There are command line options:

bitcoin -addnode=1.2.3.4    to tell bitcoin about a node to connect to
bitcoin -connect=1.2.3.4    connect only to the specified node(s)

You can use more than one of these, for instance
bitcoin -connect=(first to try) -connect=(next to try) ...

You can specify non-routable IPs with -connect like 192.168.x.x, so if you had a server farm and you wanted one server to connect to the world and the rest to connect to the one server, you could do that.

In particular, -addnode is needed if you're always going to connect through TOR, since the IRC server blocks all the TOR exit nodes.  To connect through TOR, you could use:

bitcoin -proxy=127.0.0.1:9050 -addnode=212.159.72.216
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!