public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Eric Lombrozo <elombrozo@gmail.com>
To: Danny Thorpe <danny.thorpe@gmail.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] User vote in blocksize through fees
Date: Sat, 13 Jun 2015 15:24:26 -0700	[thread overview]
Message-ID: <4A6DFE58-02F6-40D5-833F-67348D722D0D@gmail.com> (raw)
In-Reply-To: <CAJN5wHVj=KfQ3_KYOKee9uq4LNPwQ7x5nGuKDHEMUqGF4LSDLg@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 2907 bytes --]

That’s exactly the problem with Bitcoin - it was supposed to be the case that users ARE the miners and node operators…but…alas…

> On Jun 13, 2015, at 3:20 PM, Danny Thorpe <danny.thorpe@gmail.com> wrote:
> 
> Please forgive my ignorance, but why should Bitcoin users have a say in block size limits?  It's the miners and Bitcoin node operators that bear the burden of managing large blocks, no?
> 
> Users voting on network parameters sounds like neighbors voting on how deep my swimming pool should be.
> 
> Thanks,
> -Danny
> 
> On Fri, Jun 12, 2015 at 11:11 AM, Peter Todd <pete@petertodd.org <mailto:pete@petertodd.org>> wrote:
> Jeff Garzik recently proposed that the upper blocksize limit be removed
> entirely, with a "soft" limit being enforced via miner vote, recorded by
> hashing power.
> 
> This mechanism within the protocol for users to have any influence over
> the miner vote. We can add that back by providing a way for transactions
> themselves to set a flag determining whether or not they can be included
> in a block casting a specific vote.
> 
> We can simplify Garzik's vote to say that one of the nVersion bits
> either votes for the blocksize to be increased, or decreased, by some
> fixed ratio (e.g 2x or 1/2x) the next interval. Then we can use a
> nVersion bit in transactions themselves, also voting for an increase or
> decrease. Transactions may only be included in blocks with an
> indentical vote, thus providing miners with a monetary incentive via
> fees to vote according to user wishes.
> 
> Of course, to cast a "don't care" vote we can either define an
> additional bit, or sign the transaction with both versions. Equally we
> can even have different versions with different fees, broadcast via a
> mechanism such as replace-by-fee.
> 
> 
> See also John Dillon's proposal for proof-of-stake blocksize voting:
> 
> https://www.mail-archive.com/bitcoin-development@lists.sourceforge.net/msg02323.html <https://www.mail-archive.com/bitcoin-development@lists.sourceforge.net/msg02323.html>
> 
> --
> 'peter'[:-1]@petertodd.org <http://petertodd.org/>
> 0000000000000000127ab1d576dc851f374424f1269c4700ccaba2c42d97e778
> 
> ------------------------------------------------------------------------------
> 
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net <mailto:Bitcoin-development@lists.sourceforge.net>
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>
> 
> 
> ------------------------------------------------------------------------------
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development


[-- Attachment #1.2: Type: text/html, Size: 4566 bytes --]

[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 842 bytes --]

  reply	other threads:[~2015-06-13 22:24 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-12 18:11 [Bitcoin-development] User vote in blocksize through fees 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 [this message]
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=4A6DFE58-02F6-40D5-833F-67348D722D0D@gmail.com \
    --to=elombrozo@gmail.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=danny.thorpe@gmail.com \
    /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