From: Peter Todd <pete@petertodd•org>
To: Chris Priest <cp368202@ohiou•edu>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] *Changing* the blocksize limit
Date: Mon, 8 Aug 2016 19:21:29 -0700 [thread overview]
Message-ID: <20160809022129.GB1858@fedora-21-dvm> (raw)
In-Reply-To: <CAAcC9ysZdnzb9HwN_pUcdws8Dvtd5xpzoPbyHP1nNew=LeTDHg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1134 bytes --]
On Sat, Aug 06, 2016 at 07:15:22AM -0700, Chris Priest via bitcoin-dev wrote:
> If the blocksize limit is to be changed to a block output limit, the
> number the limit is set to should be roughly the amount of outputs
> that are found in 1MB blocks today. This way, the change should be
The largest output on testnet is a bit under 1MB, and encodes a certain
well-known love song...
In many circumstances(1) miners have an incentive to create larger blocks that
take their competitors longer to receive and validate, so protocol-level block
limits need to take all these potential DoS vectors into account; serialized
size is one of the most fundemental things that needs to be limited.
> considered non-controversial. I think its silly that some people think
> its a good thing to keep usage restricted, but again, it is what it
> is.
As mentioned above, and explained in detail in my recent blog post(1),
restrictions are needed to keep a level playing field between all miners.
1) https://petertodd.org/2016/block-publication-incentives-for-miners
--
https://petertodd.org 'peter'[:-1]@petertodd.org
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
prev parent reply other threads:[~2016-08-09 2:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-06 14:15 Chris Priest
2016-08-06 18:52 ` Luke Dashjr
2016-08-09 2:21 ` Peter Todd [this message]
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=20160809022129.GB1858@fedora-21-dvm \
--to=pete@petertodd$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=cp368202@ohiou$(echo .)edu \
/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