jgarzik (OP)
Legendary
Offline
Activity: 1596
Merit: 1091
|
|
March 09, 2011, 03:44:56 AM |
|
URL: http://yyz.us/bitcoin/patch.bitcoin-dnsseedThis patch adds "-dnsseed" command line argument, which causes bitcoin to read P2P node addresses from DNS A records retrieved via lookups against a precompiled list of DNS names. Presumably, trusted community members running long-running nodes could list their nodes here. Also, someone might wish to create a service that examines current P2P addresses from addr.dat, and exports a random selection of fresh nodes via DNS.
|
Jeff Garzik, Bloq CEO, former bitcoin core dev team; opinions are my own. Visit bloq.com / metronome.io Donations / tip jar: 1BrufViLKnSWtuWGkryPsKsxonV2NQ7Tcj
|
|
|
|
|
|
Whoever mines the block which ends up containing your transaction will get its fee.
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
nanotube
|
|
March 09, 2011, 03:48:31 AM |
|
nice idea!
|
|
|
|
mndrix
Michael Hendricks
VIP
Sr. Member
Offline
Activity: 447
Merit: 258
|
|
March 09, 2011, 04:06:44 AM |
|
For anyone testing the patch, you can also use bitseed.ndrix.com and bitseed.jjgames.com which both point to long-running nodes
|
|
|
|
jgarzik (OP)
Legendary
Offline
Activity: 1596
Merit: 1091
|
|
March 09, 2011, 04:29:02 AM |
|
in addition to hard-coded list, what do you think about my idea of having a convention of using for bootstrap a list of DNS names like fallback.bitcoin.<tld> or bootstrap.bitcoin.<tld> for every known TLD, there are couple of hundreds of them.
Seems easier to abuse than just hardcoded trusted DNS names, where site owners proactively indicate interest in being listed. Long term, I hope some community members step up to - administer a domain bitseed.example.com
- use https://github.com/gavinandresen/bitcointools to dump bitcoin's address database
- select 5-6 "fresh" addresses on port 8333
- dynamically update your DNS bitseed.example.com to list those 5-6 addresses in A records
This sort of dynamic P2P sampling + export is preferred over simply listing long-running node jgarziks_node.example.com.
|
Jeff Garzik, Bloq CEO, former bitcoin core dev team; opinions are my own. Visit bloq.com / metronome.io Donations / tip jar: 1BrufViLKnSWtuWGkryPsKsxonV2NQ7Tcj
|
|
|
jgarzik (OP)
Legendary
Offline
Activity: 1596
Merit: 1091
|
|
March 10, 2011, 07:23:46 PM |
|
As of now I am hosting #host bitseed.bitcoin.org.uk bitseed.bitcoin.org.uk has address 69.163.132.101 bitseed.bitcoin.org.uk has address 109.75.176.193 bitseed.bitcoin.org.uk has address 217.157.1.202 bitseed.bitcoin.org.uk has address 174.120.185.74 bitseed.bitcoin.org.uk has address 69.164.218.197 bitseed.bitcoin.org.uk has address 178.18.90.41 bitseed.bitcoin.org.uk has address 142.58.248.28 bitseed.bitcoin.org.uk has address 91.85.220.84 bitseed.bitcoin.org.uk has address 178.63.62.15 bitseed.bitcoin.org.uk has address 178.63.15.200 suitable hosts are taken from https://en.bitcoin.it/wiki/Fallback_NodesFeel free to use for testing and in production. Added to DNS seed list. That's just the sort of DNS seed I was hoping for, thanks.
|
Jeff Garzik, Bloq CEO, former bitcoin core dev team; opinions are my own. Visit bloq.com / metronome.io Donations / tip jar: 1BrufViLKnSWtuWGkryPsKsxonV2NQ7Tcj
|
|
|
twobits
|
|
August 19, 2011, 12:23:53 PM |
|
As of now I am hosting #host bitseed.bitcoin.org.uk bitseed.bitcoin.org.uk has address 69.163.132.101 bitseed.bitcoin.org.uk has address 109.75.176.193 bitseed.bitcoin.org.uk has address 217.157.1.202 bitseed.bitcoin.org.uk has address 174.120.185.74 bitseed.bitcoin.org.uk has address 69.164.218.197 bitseed.bitcoin.org.uk has address 178.18.90.41 bitseed.bitcoin.org.uk has address 142.58.248.28 bitseed.bitcoin.org.uk has address 91.85.220.84 bitseed.bitcoin.org.uk has address 178.63.62.15 bitseed.bitcoin.org.uk has address 178.63.15.200 suitable hosts are taken from https://en.bitcoin.it/wiki/Fallback_NodesFeel free to use for testing and in production. Seems the link to the patch now gives a 404 record so I can't look at it. If I am understanding what is proposed here it seems a good idea. However the above is not the right record type. It should be using SRV records not A records, this also lets the record specific the port number, so that need not be fixed.
|
█████ █████ ███████ █████ ███ █████████████ █████ ██ █████████████████ █████ █ ██████ ██████ █████ ████ ████ █████████████ █████ ████ █████████████ █████ ████ █████████████ █████ ████ █████ █████ █████ █ ██████ ███████ █████ ██ ███████████ █████ █████ ███ █████████ ████ █████ █████ ███████ ██ | | | ███ ███ ███ ███ ███ ███ ███ ███ ███ | | | | | | ███ ███ ███ ███ ███ ███ ███ ███ ███ | | ►WhitePaper ►One-Pager | ███ ███ ███ ███ ███ ███ ███ ███ ███ | | | | ███ ███ ███ ███ ███ ███ ███ ███ ███ | | ███ ███ ███ ███ ███ ███ ███ ███ ███ | █████ █████ ███████ █████ ███ █████████████ █████ ██ █████████████████ █████ █ ██████ ██████ █████ ████ ████ █████████████ █████ ████ █████████████ █████ ████ █████████████ █████ ████ █████ █████ █████ █ ██████ ███████ █████ ██ ███████████ █████ █████ ███ █████████ ████ █████ █████ ███████ ██ |
|
|
|
|
jgarzik (OP)
Legendary
Offline
Activity: 1596
Merit: 1091
|
|
August 20, 2011, 02:38:33 AM |
|
Seems the link to the patch now gives a 404 record so I can't look at it. If I am understanding what is proposed here it seems a good idea. However the above is not the right record type. It should be using SRV records not A records, this also lets the record specific the port number, so that need not be fixed.
SRV records would be nice... ...but it is difficult to make that work in a cross-platform manner. "A" records have a higher Just Works(tm) value, even if we are forced to compromise and hardcode port 8333.
|
Jeff Garzik, Bloq CEO, former bitcoin core dev team; opinions are my own. Visit bloq.com / metronome.io Donations / tip jar: 1BrufViLKnSWtuWGkryPsKsxonV2NQ7Tcj
|
|
|
theymos
Administrator
Legendary
Offline
Activity: 5194
Merit: 12976
|
|
August 20, 2011, 03:07:33 AM |
|
"A" records have a higher Just Works(tm) value, even if we are forced to compromise and hardcode port 8333.
It also wouldn't be too difficult to brute-force all port numbers if none of the peers support 8333 (which probably indicates that the ISP is blocking 8333).
|
1NXYoJ5xU91Jp83XfVMHwwTUyZFK64BoAD
|
|
|
marcus_of_augustus
Legendary
Offline
Activity: 3920
Merit: 2348
Eadem mutata resurgo
|
|
August 20, 2011, 08:57:42 AM |
|
Maybe an application for Namecoin "trust-noone" local, dns look-ups.
|
|
|
|
tnkflx
|
|
August 21, 2011, 10:55:56 AM |
|
We could also get our own tld via http://www.opennicproject.org/... For instance, .btc or .bitcoin or whatever
|
| Operating electrum.be & us.electrum.be |
|
|
|
zwierzak
Newbie
Offline
Activity: 24
Merit: 0
|
|
August 21, 2011, 04:45:34 PM |
|
|
|
|
|
|