From: Peter Todd <pete@petertodd.org>
To: Chun Wang <1240902@gmail.com>
Cc: bitcoin-dev@lists.linuxfoundation.org, greg@xiph.org
Subject: Re: [bitcoin-dev] Dynamically Controlled Bitcoin Block Size Max Cap [BIP 1xx - Draft]
Date: Tue, 25 Aug 2015 13:16:43 -0700 [thread overview]
Message-ID: <20150825201643.GC11083@muck> (raw)
In-Reply-To: <CAFzgq-x9GBbqARyhMgfSPc=wYeBgzXy4VUQ0D76GC+TCAxWDuA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 779 bytes --]
On Tue, Aug 25, 2015 at 05:19:28PM +0800, Chun Wang via bitcoin-dev wrote:
> Proposal 1 looks good, but tx fee collected can be manipulated by
> miners. I like the idea next block collect the tx fee from previous
> block.
What would you think of an approach like John Dillon's proposal to
explicitly give the economic majority of coin holders a vote for the max
blocksize? Miners could still vote BIP100 style for what max they were
willing to use, limited in turn by the vote of the economic majority.
I think in principle that would give all parties a clear voice in the
matter, which in turn makes whatever the result is more legitimit and
less controversial.
--
'peter'[:-1]@petertodd.org
000000000000000013a6653562bcb4bda7570118635eeaa8597108576bc9733b
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 650 bytes --]
next prev parent reply other threads:[~2015-08-25 20:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-25 9:07 [bitcoin-dev] Dynamically Controlled Bitcoin Block Size Max Cap [BIP 1xx - Draft] Upal Chakraborty
2015-08-25 9:19 ` Chun Wang
2015-08-25 20:16 ` Peter Todd [this message]
2015-08-25 20:26 ` Matt Whitlock
2015-08-25 20:37 ` Peter Todd
2015-08-25 21:14 ` Matt Whitlock
2015-08-25 21:28 ` Eric Voskuil
2015-08-25 21:18 ` Simon Liu
2015-08-25 21:44 ` Chun Wang
2015-08-26 0:29 ` Peter Todd
2015-08-26 6:28 ` Hector Chu
2015-08-26 12:19 ` Upal Chakraborty
2015-08-27 15:09 ` Upal Chakraborty
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=20150825201643.GC11083@muck \
--to=pete@petertodd.org \
--cc=1240902@gmail.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=greg@xiph.org \
/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