From: Eric Lombrozo <elombrozo@gmail•com>
To: Jeff Garzik <jgarzik@bitpay•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] User vote in blocksize through fees
Date: Sat, 13 Jun 2015 22:20:37 -0700 [thread overview]
Message-ID: <04527D50-0118-4E74-8226-3E29B29CC7D8@gmail.com> (raw)
In-Reply-To: <CAJHLa0Oh0wm_1SynFdCu+WkVD-gTGk0ZUNgQV0GVj0-3zL=zzw@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 739 bytes --]
I definitely think we need some voting system for metaconsensus…but if we’re going to seriously consider this we should look at the problem much more generally. Using false choices doesn’t really help, though ;)
- Eric Lombrozo
> On Jun 13, 2015, at 10:13 PM, Jeff Garzik <jgarzik@bitpay•com> wrote:
>
> On Sun, Jun 14, 2015 at 1:08 AM, Eric Lombrozo <elombrozo@gmail•com <mailto:elombrozo@gmail•com>> wrote:
> 2) BIP100 has direct economic consequences…and particularly for miners. It lends itself to much greater corruptibility.
>
>
> What is the alternative? Have a Chief Scientist or Technical Advisory Board choose what is a proper fee, what is a proper level of decentralization, a proper growth factor?
[-- Attachment #1.2: Type: text/html, Size: 3473 bytes --]
[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 842 bytes --]
next prev parent reply other threads:[~2015-06-14 5:20 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
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 [this message]
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=04527D50-0118-4E74-8226-3E29B29CC7D8@gmail.com \
--to=elombrozo@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=jgarzik@bitpay$(echo .)com \
/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