From: Luke Dashjr <luke@dashjr•org>
To: bitcoin-dev@lists•linuxfoundation.org,
Tom Zander <tomz@freedommail•ch>, "t. khan" <teekhan42@gmail•com>
Subject: Re: [bitcoin-dev] BIP - 'Block75' - New algorithm
Date: Mon, 2 Jan 2017 21:19:10 +0000 [thread overview]
Message-ID: <201701022119.11115.luke@dashjr.org> (raw)
In-Reply-To: <1944321.hguq3JoYe1@cherry>
On Monday, January 02, 2017 8:35:40 PM Tom Zander via bitcoin-dev wrote:
> A maximum is needed, yes. But does it have to be part of the protocol?
> A simple policy which is set by node operators (reject block if greater
> than X bytes) will solve this just fine, no?
If you reject a block based on a particular condition, that is BY DEFINITION
part of the consensus protocol, and NOT a policy. The protocol is literally
the set of rules by which blocks are determined to be valid or invalid.
Policies are things that can vary node-to-node without affecting the validity
judgement of blocks.
On Monday, January 02, 2017 8:41:42 PM t. khan wrote:
> On Mon, Jan 2, 2017 at 3:04 PM, Luke Dashjr <luke@dashjr•org> wrote:
> > It would probably behave as an ever-increasing block size limit. Spam has
> > typically filled blocks to the max, and miners have stopped
> > self-enforcing reasonable limits.
>
> Using the growth rate over the last year as a model (
> https://blockchain.info/charts/avg-block-size?daysAverageString=14 ),
> Block75 would also have frequently decreased the limit. Though, yes, more
> transactions would equal larger blocks over time, but that's the entire
> point of this.
Then it doesn't solve the actual problems of either miner spam or growth in
resource requirements, which are the entire purpose of the block size limit.
> What is your definition of "spam"?
Anything that consumes more data than necessary to properly convey the
intended transfer of value (bitcoins) from one entity to another, including
all data that is not intended for such a purpose.
> > I doubt you'll get consensus for such a fundamentally broken proposal.
> > I certainly don't foresee any circumstance where I could reasonably
> > support it... The block size limit exists to restrict miners; it makes no
> > sense to put it in their control.
>
> Specifically, what is broken about it?
Putting group X in control of a limit that exists for the sole purpose of
restricting group X.
> There would still be a block size limit, it would just change slightly
> every two weeks. I agree that miners shouldn't have control of this, and
> Block75 doesn't give them any (at least none they can make a profit on).
It gives miners complete control over the limit. They can make blocks of any
size (within the current limit), thus triggering the conditions by which your
proposal would raise the limit further.
Luke
next prev parent reply other threads:[~2017-01-02 21:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-02 18:04 t. khan
2017-01-02 19:01 ` Tom Zander
2017-01-02 19:32 ` t. khan
2017-01-02 20:35 ` Tom Zander
2017-01-02 21:05 ` t. khan
2017-01-02 22:33 ` Tom Zander
2017-01-02 21:19 ` Luke Dashjr [this message]
2017-01-02 22:01 ` Tom Zander
2017-01-03 14:28 ` t. khan
2017-02-13 11:21 ` Hampus Sjöberg
2017-01-02 20:04 ` Luke Dashjr
2017-01-02 20:41 ` t. khan
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=201701022119.11115.luke@dashjr.org \
--to=luke@dashjr$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=teekhan42@gmail$(echo .)com \
--cc=tomz@freedommail$(echo .)ch \
/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