public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Gavin Andresen <gavinandresen@gmail.com>
To: Pieter Wuille <pieter.wuille@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 13:21:46 -0400	[thread overview]
Message-ID: <CABsx9T1=+S+dAdwASECUCkrVaMFT0TcmL7MiwnCuCx0MkF6sWw@mail.gmail.com> (raw)
In-Reply-To: <CAPg+sBi5fYHGLv4wtWbWE7jov8CX=q9UX=vhxDVepG6JfX30+g@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 506 bytes --]

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?

Or, even simpler, why couldn't the little miners just run their
block-assembling-and-announcing code on the other high-bandwidth-side of
the bandwidth bottleneck?

-- 
--
Gavin Andresen

[-- Attachment #2: Type: text/html, Size: 761 bytes --]

  reply	other threads:[~2015-06-12 17:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-12 16:51 [Bitcoin-development] Mining centralization pressure from non-uniform propagation speed Pieter Wuille
2015-06-12 17:21 ` Gavin Andresen [this message]
2015-06-12 18:30   ` Peter Todd
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='CABsx9T1=+S+dAdwASECUCkrVaMFT0TcmL7MiwnCuCx0MkF6sWw@mail.gmail.com' \
    --to=gavinandresen@gmail.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=pieter.wuille@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