From: Gregory Maxwell <gmaxwell@gmail•com>
To: Arnoud Kouwenhoven - Pukaki Corp <arnoud@pukaki•bz>
Cc: Arnoud Kouwenhoven - Pukaki Corp via bitcoin-dev
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Idea: Efficient bitcoin block propagation
Date: Wed, 5 Aug 2015 20:16:34 +0000 [thread overview]
Message-ID: <CAAS2fgQLNH+rivNNTFz6xt_9SxO3fFj7-3z7A-_B_2X2x-6M5w@mail.gmail.com> (raw)
In-Reply-To: <CALwsPgm6xcBfLXZTNTZ40R_s3oUawE0ANZycDWpSo0cXZ+=-Vg@mail.gmail.com>
On Wed, Aug 5, 2015 at 7:53 PM, Arnoud Kouwenhoven - Pukaki Corp via
bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org> wrote:
> Thanks for the reply. My understanding is that the bitcoin relay network is
> a backbone of connected high speed servers to increase the rate at which
> transactions and new blocks propagate - and remove a number of delays in
> processing. But it would still require the miners to download the entire
> block before building on top of it with any degree of confidence.
Your understanding is outdated.
The relay network includes an optimized transmission protocol which
enables sending the "entire" block typically in just a smal number of
bytes (much smaller than the summaries you suggest, which still leave
the participants needing to send the block).
E.g. block 000ce90846 was 999950 bytes and the relay network protocol
sent it using at most 4906 bytes.
No trust is required in this scheme because the entire block is
communicated using only a couple packets.
The current scheme is highly simplified and its efficiency could be
increased greatly with small improvements, or if miners created blocks
in an aware manner.... but with a maximum size blocks turning into 5kb
with the current setup, there hardly appears to be a reason to do so
right now.
Ultimately there is no need for information communicated with a block
at discovery time proportional to the size of the block; with the
right affordances it can be accomplished with a small constant amount
of data.
If not for this already being deployed I personally believe the
network would have already fallen into complete centeralization as a
response to larger blocks: this was constructed and deployed in order
to pull the network back from having a single pool with more than half
the hashrate.
next prev parent reply other threads:[~2015-08-05 20:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-05 19:07 Arnoud Kouwenhoven - Pukaki Corp
2015-08-05 19:27 ` Matt Corallo
2015-08-05 19:53 ` Arnoud Kouwenhoven - Pukaki Corp
2015-08-05 20:16 ` Gregory Maxwell [this message]
2015-08-05 21:19 ` Arnoud Kouwenhoven - Pukaki Corp
2015-08-05 22:14 ` Gregory Maxwell
2015-08-06 17:16 ` Sergio Demian Lerner
2015-08-06 17:33 ` Olaoluwa Osuntokun
2015-08-06 18:17 ` Tom Harding
2015-08-06 18:42 ` Gregory Maxwell
2015-08-06 20:50 ` Matt Corallo
2015-08-06 20:55 ` Matt Corallo
2015-08-06 20:38 ` Matt Corallo
2015-08-07 7:14 ` jl2012
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=CAAS2fgQLNH+rivNNTFz6xt_9SxO3fFj7-3z7A-_B_2X2x-6M5w@mail.gmail.com \
--to=gmaxwell@gmail$(echo .)com \
--cc=arnoud@pukaki$(echo .)bz \
--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