Title: addr.txt Post by: ProfMac on February 06, 2013, 04:25:12 PM I started the Satoshi client, bitcoin-qt. The file bitcoin.conf contains the line onlynet=IPv6.
It ran for almost a week, and as of this morning it is synchronized. This is significantly longer than the times I am hearing from other people. I am running XP (SP3) Pentium(R) 4 CPU 3.00GHz 2.99 GHz, 3.50 GB of RAM What I would like to do next is to use addr.txt to pre-load some peer addresses. I can write my own code to harvest addresses from debug.log and stuff them into mySQL, and with more time I can read the source and read peers.dat, but it seems that some of the developers would already be able to make addr.txt. Actually, it seems that bitcoin-qt should be able to produce this file, as a symmetric operation to being able to read it. Can I get a copy of a windows binary (preferred) or a pointer to the source for Ubuntu 12.04 (less preferred) Thanks. Title: Re: addr.txt Post by: deepceleron on February 06, 2013, 05:36:38 PM Additional nodes can be specified with the command line or bitcoin.conf option "addnode=10.0.0.1:8333". This is not guaranteed to open a connection, the other Bitcoin nodes still have to like you and be wanting more connections. IP addresses quickly become obsolete, a large number of Bitcoin users are on dynamic IP addresses or don't run Bitcoin full time.
You can throw something like this into your bitcoin.conf file if you want to attempt connection to your own list of IP addresses in addition to the peer-finding methodology in Bitcoin, which already works quite well. Code: maxconnections=500 Fallback nodes are listed here: https://en.bitcoin.it/wiki/Fallback_Nodes You can also grab other's lists of connected IP addresses: http://blockchain.info/connected-nodes http://nodes.bitcoin.st/ http://pastehtml.com/view/c7rf4x1gc.rtxt If you already have another machine that is running and updated, you do not need to connect to the public network at all, your second copy of Bitcoin can connect exclusively to the local machine with the option connect=192.168.1.100 (whatever the IP address is of the first Bitcoin). Bitcoin binaries are available at http://bitcoin.org. Title: Re: addr.txt Post by: gmaxwell on February 07, 2013, 05:54:22 AM Additional nodes can be specified with the command line or bitcoin.conf option They can also be placed in an addr.txt, as the OP asked about. Addr.txt has the advantage of just feeding the database, not forcing connections like addnode does. Unless there is some attack on bitcoin bootstrapping there probably isn't a reason to use addr.txt, however. Adding a long list of addnodes like that is somewhat inadvisable, it wastes resources on the network... Title: Re: addr.txt Post by: Diapolo on February 07, 2013, 07:02:35 AM Shouldn't your switch be onlynet="IPv6"?
Dia Title: Re: addr.txt Post by: ProfMac on February 07, 2013, 12:21:17 PM Shouldn't your switch be onlynet="IPv6"? Dia I'm not sure if the parameters are supposed to be quoted or not. I do like to be careful about such things, so after I get things minimally working I will read through from the beginning again. However, it does work without the quotes. I have only IPv6 addresses in debug.log. It seems that IPv6 is pretty well established in the Bitcoin world. Title: Re: addr.txt Post by: ProfMac on February 08, 2013, 03:33:53 PM Shouldn't your switch be onlynet="IPv6"? Dia I checked this. Bitcoin-qt will not start if the quotes are included. Title: Re: addr.txt Post by: Diapolo on February 08, 2013, 03:45:42 PM Shouldn't your switch be onlynet="IPv6"? Dia I checked this. Bitcoin-qt will not start if the quotes are included. Strange, via command-line I always used -onlynet="IPv6". Perhaps I didn't need the quotes, but at least it was working :). Dia Title: Re: addr.txt Post by: dserrano5 on February 08, 2013, 07:44:00 PM Strange, via command-line I always used -onlynet="IPv6". Perhaps I didn't need the quotes, but at least it was working :). The quotes are part of the shell syntax and are removed by it, so bitcoin doesn't see them. |