From: Arne Brutschy <abrutschy@xylon•de>
To: bitcoin-development@lists•sourceforge.net
Subject: [Bitcoin-development] Removing transaction data from blocks
Date: Fri, 08 May 2015 16:01:01 +0200 [thread overview]
Message-ID: <554CC19D.2010306@xylon.de> (raw)
Hello,
At DevCore London, Gavin mentioned the idea that we could get rid of
sending full blocks. Instead, newly minted blocks would only be
distributed as block headers plus all hashes of the transactions
included in the block. The assumption would be that nodes have already
the majority of these transactions in their mempool.
The advantages are clear: it's more efficient, as we would send
transactions only once over the network, and it's fast as the resulting
blocks would be small. Moreover, we would get rid of the blocksize limit
for a long time.
Unfortunately, I am too ignorant of bitcoin core's internals to judge
the changes required to make this happen. (I guess we'd require a new
block format and a way to bulk-request missing transactions.)
However, I'm curious to hear what others with a better grasp of bitcoin
core's internals have to say about it.
Regards,
Arne
next reply other threads:[~2015-05-08 14:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-08 14:01 Arne Brutschy [this message]
2015-05-08 14:52 ` Pieter Wuille
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=554CC19D.2010306@xylon.de \
--to=abrutschy@xylon$(echo .)de \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/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