From: Wladimir <laanwj@gmail.com>
To: Gregory Maxwell <gmaxwell@gmail.com>
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Fwd: Outbound connections rotation
Date: Mon, 18 Aug 2014 20:38:40 +0200 [thread overview]
Message-ID: <CA+s+GJAV+YBDmDVk9Nvo_qAjk=WEBPhX-kqkX1fiUsLfGvEUkw@mail.gmail.com> (raw)
In-Reply-To: <CAAS2fgT5-s-uukP8uTRKJ+pzwG-f9knetH44qQ78HsctG9_cZA@mail.gmail.com>
> The optimal strategy for avoiding linkages (ignoring tor, again), is
> to randomly pick a different peer for each transaction and relay the
> transaction only to that peer. This can (and probably should) be
> distinct from your normal network connectivity.
It already happens with 8 peers that if you have lousy peers, the
transaction doesn't reach the network on the first broadcasting. When
sending to only one random peer it will likely be even worse.
I guess the wallet could send out the transaction 'staggered' over
time. It could pick a random new node, broadcast the transaction, wait
a bit, pick a new node, broadcast the transaction until it is comes
back through one of the other peers.
Separating the transaction broadcasting (of the wallet) from, for
example, the nodes used to request blocks from could make sense. Maybe
doubly so if bloom filters are involved.
Wladimir
next prev parent reply other threads:[~2014-08-18 18:38 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
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 [this message]
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='CA+s+GJAV+YBDmDVk9Nvo_qAjk=WEBPhX-kqkX1fiUsLfGvEUkw@mail.gmail.com' \
--to=laanwj@gmail.com \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=gmaxwell@gmail.com \
/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