From: Peter Todd <pete@petertodd•org>
To: Matt Whitlock <bip@mattwhitlock•name>
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] User vote in blocksize through fees
Date: Fri, 12 Jun 2015 19:34:21 +0100 [thread overview]
Message-ID: <20150612183421.GE19199@muck> (raw)
In-Reply-To: <23144512.HX7dfatEFr@crushinator>
[-- Attachment #1: Type: text/plain, Size: 1380 bytes --]
On Fri, Jun 12, 2015 at 02:22:36PM -0400, Matt Whitlock wrote:
> Why should miners only be able to vote for "double the limit" or "halve" the limit? If you're going to use bits, I think you need to use two bits:
>
> 0 0 = no preference ("wildcard" vote)
> 0 1 = vote for the limit to remain the same
> 1 0 = vote for the limit to be halved
> 1 1 = vote for the limit to be doubled
>
> User transactions would follow the same usage. In particular, a user vote of "0 0" (no preference) could be included in a block casting any vote, but a block voting "0 0" (no preference) could only contain transactions voting "0 0" as well.
Sounds like a good encoding to me. Taking the median of the three
options, and throwing away "don't care" votes entirely, makes sense.
> Incidentally, I love this idea, as it addresses a concern I immediately had with Jeff's proposal, which is that it hands control exclusively to the miners. And your proposal here fixes that shortcoming in a economically powerful way: miners lose out on fees if they don't represent the wishes of the users.
Thanks! I personally expect disaster to ensue with this kind of
proposal, but I'm less concerned if the disaster is something users
explicitly allowed to happen in a consensual way.
--
'peter'[:-1]@petertodd.org
0000000000000000127ab1d576dc851f374424f1269c4700ccaba2c42d97e778
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 650 bytes --]
next prev parent reply other threads:[~2015-06-12 18:34 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-12 18:11 Peter Todd
2015-06-12 18:20 ` Mark Friedenbach
2015-06-12 18:26 ` Matt Whitlock
2015-06-12 18:36 ` Peter Todd
2015-06-12 18:56 ` Jannes Faber
[not found] ` <CABr1YTfowMqgDZoWhDXiM0Bd3dwhVo6++FOvLntGc2HkApEbGw@mail.gmail.com>
2015-06-12 20:04 ` Eric Lombrozo
2015-06-12 23:01 ` Vincent Truong
2015-06-12 23:11 ` Luke Dashjr
2015-06-12 23:23 ` Aaron Gustafson
2015-06-12 18:22 ` Matt Whitlock
2015-06-12 18:34 ` Peter Todd [this message]
2015-06-12 18:36 ` Matt Whitlock
2015-06-12 18:39 ` Benjamin
2015-06-12 18:47 ` Peter Todd
2015-06-12 18:44 ` Peter Todd
2015-06-12 18:52 ` Matt Whitlock
2015-06-12 18:54 ` Matt Whitlock
2015-06-12 18:56 ` Aaron Gustafson
2015-06-13 22:20 ` Danny Thorpe
2015-06-13 22:24 ` Eric Lombrozo
2015-06-14 4:55 ` Chun Wang
2015-06-14 4:59 ` Jeff Garzik
2015-06-14 5:08 ` Eric Lombrozo
2015-06-14 5:13 ` Jeff Garzik
2015-06-14 5:20 ` Eric Lombrozo
2015-06-14 5:36 ` Jeff Garzik
2015-06-14 10:06 ` Mats Henricson
2015-06-14 10:34 ` Benjamin
2015-06-14 15:07 ` Jeff Garzik
2015-06-14 21:59 ` odinn
2015-06-14 20:10 ` Eric Lombrozo
2015-06-14 14:42 ` Jeff Garzik
2015-06-14 22:26 ` Mike Hearn
2015-06-15 3:59 ` Eric Lombrozo
2015-06-14 4:16 ` Stephen
2015-06-14 4:50 ` Eric Lombrozo
2015-06-14 4:56 ` Jeff Garzik
2015-06-14 7:19 ` Ashley Holman
2015-06-13 23:57 Raystonn
2015-06-14 4:28 ` odinn
2015-06-14 5:46 ` Aaron Voisine
2015-06-14 21:38 ` odinn
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=20150612183421.GE19199@muck \
--to=pete@petertodd$(echo .)org \
--cc=bip@mattwhitlock$(echo .)name \
--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