From: Peter Todd <pete@petertodd•org>
To: Gavin Andresen <gavinandresen@gmail•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Mining centralization pressure from non-uniform propagation speed
Date: Fri, 12 Jun 2015 19:30:54 +0100 [thread overview]
Message-ID: <20150612183054.GD19199@muck> (raw)
In-Reply-To: <CABsx9T1=+S+dAdwASECUCkrVaMFT0TcmL7MiwnCuCx0MkF6sWw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 793 bytes --]
On Fri, Jun 12, 2015 at 01:21:46PM -0400, Gavin Andresen wrote:
> Nice work, Pieter. You're right that my simulation assumed bandwidth for
> 'block' messages isn't the bottleneck.
>
> But doesn't Matt's fast relay network (and the work I believe we're both
> planning on doing in the near future to further optimize block propagation)
> make both of our simulations irrelevant in the long-run?
Then simulate first the relay network assuming 100% of txs use it, and
secondly, assuming 100%-x use it.
For instance, is it in miners' advantage in some cases to sabotage the
relay network? The analyse say yes, so lets simulate that. Equally even
the relay network isn't instant.
--
'peter'[:-1]@petertodd.org
0000000000000000127ab1d576dc851f374424f1269c4700ccaba2c42d97e778
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 650 bytes --]
next prev parent reply other threads:[~2015-06-12 18:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-12 16:51 Pieter Wuille
2015-06-12 17:21 ` Gavin Andresen
2015-06-12 18:30 ` Peter Todd [this message]
2015-06-12 18:39 ` Pieter Wuille
2015-06-12 18:01 ` Peter Todd
2015-06-12 18:24 ` Mike Hearn
2015-06-12 18:26 ` Pieter Wuille
2015-06-12 18:27 ` Mike Hearn
2015-06-14 17:45 ` Jonas Nick
2015-06-18 22:00 ` Tom Harding
2015-06-19 1:31 ` Yifu Guo
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=20150612183054.GD19199@muck \
--to=pete@petertodd$(echo .)org \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=gavinandresen@gmail$(echo .)com \
/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