From: Gregory Maxwell <greg@xiph•org>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIP proposal - Dandelion: Privacy Preserving Transaction Propagation
Date: Tue, 26 Jun 2018 05:20:02 +0000 [thread overview]
Message-ID: <CAAS2fgRHgTFvR7TbrObEpQxU10XE487jw=Y5pYgdoJ=BhhAQow@mail.gmail.com> (raw)
In-Reply-To: <CAGq_bNJv6z5uTX-0feNMVFNxtDcFJSuzS14AE68hxnBu9WP=0g@mail.gmail.com>
On Tue, Jun 26, 2018 at 12:12 AM, Bradley Denby via bitcoin-dev
<bitcoin-dev@lists•linuxfoundation.org> wrote:
> That's right, the idea is to choose Dandelion relays independently from
> whether they support Dandelion. If the chosen nodes do not support
> Dandelion, then the transactions are fluffed. Otherwise, the transactions
> are relayed along a stem.
I don't see any problem with doing that... Although an additional
countermeasure we're likely to take against attacks on partial
deployment is that we'd likely make the wallet's use of stem
forwarding be a configuration option which is initially hidden and set
to off. In a subsistent release after dandelion propagation is widely
deployed we'd unhide the option and default it to on. This way users
don't begin using it until the deployment is relatively dense.
I believe this approach is a is sufficient such that it could always
select out-peers that were dandelion capable without harm, but at the
same time I also don't see a reason that we can't do both.
(in fact, for privacy reasons we might want to three-stage the
deployment, with the use of dandelion by wallets having a setting of
off, sometimes, or always so that attackers can't so easily correlate
the use of dandelion with upgrades.)
next prev parent reply other threads:[~2018-06-26 5:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-10 12:59 Bradley Denby
2018-06-04 20:29 ` Bradley Denby
2018-07-05 14:50 ` Neudecker, Till (TM)
2018-06-06 4:01 ` Pieter Wuille
2018-06-11 14:31 ` Bradley Denby
2018-06-12 1:05 ` Pieter Wuille
2018-06-26 0:12 ` Bradley Denby
2018-06-26 5:20 ` Gregory Maxwell [this message]
[not found] <mailman.3774.1530901879.19027.bitcoin-dev@lists.linuxfoundation.org>
2018-07-08 12:50 ` Giulia Fanti
-- strict thread matches above, loose matches on Subject: below --
2017-09-21 2:10 Giulia Fanti
2017-06-12 14:46 Andrew Miller
2017-06-13 1:00 ` Gregory Maxwell
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='CAAS2fgRHgTFvR7TbrObEpQxU10XE487jw=Y5pYgdoJ=BhhAQow@mail.gmail.com' \
--to=greg@xiph$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/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