From: Luke Dashjr <luke@dashjr.org>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Zero-Conf for Full Node Discovery
Date: Tue, 26 May 2015 05:23:04 +0000 [thread overview]
Message-ID: <201505260523.05104.luke@dashjr.org> (raw)
In-Reply-To: <CAEY8wq40vyG8CFZ7U1Z3hhF_ziSqEQ3GDpXLwm1MAVtK03aT-A@mail.gmail.com>
On Tuesday, May 26, 2015 4:46:22 AM Kevin Greene wrote:
> This is something you actually don't want. In order to make it as difficult
> as possible for an attacker to perform a sybil attack, you want to choose a
> set of peers that is as diverse, and unpredictable as possible.
It doesn't hurt to have a local node or two, though. Might as well to improve
propagation, while maintaining the other peers to avoid sybil attacks.
Luke
next prev parent reply other threads:[~2015-05-26 5:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-26 4:06 [Bitcoin-development] Zero-Conf for Full Node Discovery Jim Phillips
2015-05-26 4:37 ` Matt Whitlock
2015-05-26 4:46 ` Kevin Greene
2015-05-26 4:56 ` Matt Whitlock
2015-05-26 5:12 ` Kevin Greene
2015-05-26 5:23 ` Luke Dashjr [this message]
2015-05-26 4:48 ` Jim Phillips
2015-05-26 4:52 ` Matt Whitlock
2015-05-26 5:15 ` Peter Todd
2015-05-26 5:47 ` Matt Whitlock
2015-05-26 10:48 ` Mike Hearn
2015-05-27 10:16 ` Louis Rossouw
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=201505260523.05104.luke@dashjr.org \
--to=luke@dashjr.org \
--cc=bitcoin-development@lists.sourceforge.net \
/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