From: "Warren Togami Jr." <wtogami@gmail.com>
To: Peter Todd <pete@petertodd.org>
Cc: "bitcoin-development@lists.sourceforge.net"
<bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Peer Discovery and Overlay
Date: Tue, 24 Dec 2013 09:11:10 -0800 [thread overview]
Message-ID: <CAEz79PqbDS=i54zNkOVwdUFaSYuGGcvwdyLGPxS1poE5hx+7LA@mail.gmail.com> (raw)
In-Reply-To: <20131224140228.GA9838@savin>
[-- Attachment #1: Type: text/plain, Size: 458 bytes --]
I was concerned about this issue so we sponsored BlueMatt to implement an
address database for bitcoinj. In the future it won't be entirely reliant
on what DNS tells it.
Warren
On Tue, Dec 24, 2013 at 6:02 AM, Peter Todd <pete@petertodd.org> wrote:
> As for node addresses being a service, that's what the DNS seeds are!
> bitcoinj clients, for instance, depend very heavily on those seeds and
> can be easily compromised in a variety of ways by them.
>
[-- Attachment #2: Type: text/html, Size: 898 bytes --]
next prev parent reply other threads:[~2013-12-24 17:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-24 8:52 [Bitcoin-development] Peer Discovery and Overlay Jeremy Spilman
2013-12-24 10:47 ` Tier Nolan
2013-12-24 14:02 ` Peter Todd
2013-12-24 17:11 ` Warren Togami Jr. [this message]
2013-12-24 17:15 ` Mike Hearn
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='CAEz79PqbDS=i54zNkOVwdUFaSYuGGcvwdyLGPxS1poE5hx+7LA@mail.gmail.com' \
--to=wtogami@gmail.com \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=pete@petertodd.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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