From: Christian Decker <decker.christian@gmail•com>
To: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] DNS seeds returning gone peers
Date: Wed, 3 Aug 2011 16:37:12 +0200 [thread overview]
Message-ID: <CALxbBHU=hBPLNCfjdfJNgO=mUd14MVJpZGA0J14OE6uZgk1k3Q@mail.gmail.com> (raw)
In-Reply-To: <CAJ1JLttf+h5J8ehmx1j5P1GiGYAUiLN=fGjSV_dLoy72XQohfA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3844 bytes --]
I'm curious whether my Non-Blocking network stack (BitDroid) isn't better
suited for detecting and tracking available peers. I have implemented
several benchmarks, including a simple peer counter listener, which would
have to be adapted to fit the DNS needs (open and check if a real peer is
listening). Being non-blocking it can open several hundreds of connections
to check reachability of the peers and at the same time keep a pool of peers
connected to listen for address broadcasts, with minimal overhead (single
thread, close to no context switches).
Just an idea :-)
Regards,
Chris
On Wed, Aug 3, 2011 at 4:18 PM, Rick Wesson
<rick@support-intelligence•com>wrote:
> Starting from bitcoinj, I have plenty of ways to publish DNS. Why sort them
> by version? Ordering from highest to lowest?
>
> how about publishing addresses under version.example.com if you version
> has a perfrence?
>
> -rick
>
>
> On Wed, Aug 3, 2011 at 7:10 AM, Mike Hearn <mike@plan99•net> wrote:
>
>> There's no project currently :-)
>>
>> Starting from Matts code is probably the way to go. It's written in PHP.
>> Alternatively, you could write a Java app for it, as there are drop-in DNS
>> serving libraries you could link with BitCoinJ+sqlite. It probably wouldn't
>> be that hard. You'd want to sort nodes by version, how long they've been
>> observed to exist, the last polling time, etc.
>>
>> On Wed, Aug 3, 2011 at 4:00 PM, Rick Wesson <
>> rick@support-intelligence•com> wrote:
>>
>>> Mike,
>>>
>>> I think I can contribute to your DNS seeding project. Could you help
>>> define long-lived peers?
>>>
>>> -rick
>>>
>>>
>>> On Wed, Aug 3, 2011 at 3:04 AM, Mike Hearn <mike@plan99•net> wrote:
>>>
>>>> This is expected to happen from time to time of course as it's
>>>> inherently racy, but there are a *lot* of bad nodes appearing in the
>>>> DNS seeds.
>>>>
>>>> $ nmap -oG /tmp/x -p 8333 `dig +short bitseed.bitcoin.org.uk
>>>> dnsseed.bluematt.me bitseed.xf2.org`
>>>> ...
>>>> Nmap done: 48 IP addresses (25 hosts up) scanned in 9.80 seconds
>>>>
>>>> $ grep -c 'closed' /tmp/x
>>>> 6
>>>>
>>>> So of 48 IPs returned only 19 are actually usable. This is slowing down
>>>> peer bringup for the Android apps, which don't currently save the addresses
>>>> of last-used peers (yes, I know we should fix this).
>>>>
>>>> I was talking to a friend a few days ago about Bitcoin, he seemed
>>>> interested. I'm hoping he might take on DNS seeding as a project. A custom
>>>> DNS server that watches the network to find long-lived peers that run the
>>>> latest version would be helpful for resolving this kind of thing.
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA
>>>> The must-attend event for mobile developers. Connect with experts.
>>>> Get tools for creating Super Apps. See the latest technologies.
>>>> Sessions, hands-on labs, demos & much more. Register early & save!
>>>> http://p.sf.net/sfu/rim-blackberry-1
>>>> _______________________________________________
>>>> Bitcoin-development mailing list
>>>> Bitcoin-development@lists•sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>>>>
>>>>
>>>
>>
>
>
> ------------------------------------------------------------------------------
> BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA
> The must-attend event for mobile developers. Connect with experts.
> Get tools for creating Super Apps. See the latest technologies.
> Sessions, hands-on labs, demos & much more. Register early & save!
> http://p.sf.net/sfu/rim-blackberry-1
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists•sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
[-- Attachment #2: Type: text/html, Size: 6331 bytes --]
prev parent reply other threads:[~2011-08-03 14:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-03 10:04 Mike Hearn
2011-08-03 11:38 ` Matt Corallo
2011-08-03 12:00 ` Mike Hearn
2011-08-03 12:15 ` Johannes Henninger
2011-08-03 12:17 ` Mike Hearn
2011-08-03 12:27 ` Caleb James DeLisle
2011-08-03 12:40 ` Mike Hearn
2011-08-03 14:00 ` Rick Wesson
2011-08-03 14:10 ` Mike Hearn
2011-08-03 14:18 ` Rick Wesson
2011-08-03 14:28 ` Douglas Huff
2011-08-03 14:39 ` Mike Hearn
2011-08-03 14:48 ` Gregory Maxwell
2011-08-03 15:32 ` Matt Corallo
2011-08-03 14:37 ` Christian Decker [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CALxbBHU=hBPLNCfjdfJNgO=mUd14MVJpZGA0J14OE6uZgk1k3Q@mail.gmail.com' \
--to=decker.christian@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox