From: Mike Hearn <mike@plan99.net>
To: Gregory Maxwell <gmaxwell@gmail.com>
Cc: Ivan Pustogarov <ivan.pustogarov@uni.lu>,
Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Outbound connections rotation
Date: Mon, 18 Aug 2014 19:27:18 +0200 [thread overview]
Message-ID: <CANEZrP07ec+Bp3yvhB=QRt_gRTJ=dWPgZiMpzzeiBNki02O3aA@mail.gmail.com> (raw)
In-Reply-To: <CAAS2fgQZaDOtoh+_oaiZh6jMOacSuHbEM=vktBdThDP_7eRH0Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 809 bytes --]
>
> Connection rotation would be fine for improving a node's knoweldge
> about available peers and making the network stronger against
> partitioning.
>
It's also the first/next step towards decentralising the DNS seeds (for SPV
clients), as it'd allow each node to explore the network and return better
quality results in getaddr.
> If you rotate where you send out your transactions then with
> very high probability a sybil pretending to be many nodes will observe
> you transmitting directly.
>
This is sort of what Tor is going through with their guard nodes and how
often to rotate them.
I think the attack Ivan is talking about does not require sybil attacks to
work though, just listening to lots of peers. Raising the bar to require
the attacker to receive lots of connections seems like a win.
[-- Attachment #2: Type: text/html, Size: 1233 bytes --]
next prev parent reply other threads:[~2014-08-18 17:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-18 16:46 [Bitcoin-development] Outbound connections rotation Ivan Pustogarov
2014-08-18 17:19 ` Jeff Garzik
2014-08-18 17:21 ` Gregory Maxwell
2014-08-18 17:27 ` Mike Hearn [this message]
2014-08-18 17:35 ` Pieter Wuille
[not found] ` <CAPg+sBgzEMAQ03GTE2j82+K2B+Dia6T0z14ZYWsBQ8z8QSVoLg@mail.gmail.com>
[not found] ` <CAAS2fgRT8OQzUkneKwpjD15aLZDivT=hgBMTB63EjN8RBrp+RQ@mail.gmail.com>
2014-08-18 18:13 ` [Bitcoin-development] Fwd: " Gregory Maxwell
2014-08-18 18:38 ` Wladimir
2014-08-18 18:37 ` [Bitcoin-development] " Ivan Pustogarov
2014-08-18 19:37 ` Gregory Maxwell
2014-08-18 20:33 ` Ivan Pustogarov
2014-08-18 20:43 ` Gregory Maxwell
2014-08-18 21:02 ` Ivan Pustogarov
2014-08-18 23:20 ` Gregory Maxwell
2014-08-20 12:59 ` [Bitcoin-development] Proposal: PoW-based throttling of addresses (was: Outbound connections rotation) Isidor Zeuner
2014-08-20 14:41 ` Mike Hearn
2014-08-23 11:53 ` Isidor Zeuner
2014-08-23 13:03 ` Mike Hearn
2014-11-13 22:52 ` Isidor Zeuner
2014-11-18 12:06 ` Mike Hearn
2014-11-27 3:29 ` Isidor Zeuner
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='CANEZrP07ec+Bp3yvhB=QRt_gRTJ=dWPgZiMpzzeiBNki02O3aA@mail.gmail.com' \
--to=mike@plan99.net \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=gmaxwell@gmail.com \
--cc=ivan.pustogarov@uni.lu \
/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