<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">That’s exactly the problem with Bitcoin - it was supposed to be the case that users ARE the miners and node operators…but…alas…<div class=""><br class=""><div class=""><div><blockquote type="cite" class=""><div class="">On Jun 13, 2015, at 3:20 PM, Danny Thorpe <<a href="mailto:danny.thorpe@gmail.com" class="">danny.thorpe@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">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? <div class=""><br class=""></div><div class="">Users voting on network parameters sounds like neighbors voting on how deep my swimming pool should be.</div><div class=""><br class=""></div><div class="">Thanks,</div><div class="">-Danny</div></div><div class="gmail_extra"><br class=""><div class="gmail_quote">On Fri, Jun 12, 2015 at 11:11 AM, Peter Todd <span dir="ltr" class=""><<a href="mailto:pete@petertodd.org" target="_blank" class="">pete@petertodd.org</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Jeff Garzik recently proposed that the upper blocksize limit be removed<br class="">
entirely, with a "soft" limit being enforced via miner vote, recorded by<br class="">
hashing power.<br class="">
<br class="">
This mechanism within the protocol for users to have any influence over<br class="">
the miner vote. We can add that back by providing a way for transactions<br class="">
themselves to set a flag determining whether or not they can be included<br class="">
in a block casting a specific vote.<br class="">
<br class="">
We can simplify Garzik's vote to say that one of the nVersion bits<br class="">
either votes for the blocksize to be increased, or decreased, by some<br class="">
fixed ratio (e.g 2x or 1/2x) the next interval. Then we can use a<br class="">
nVersion bit in transactions themselves, also voting for an increase or<br class="">
decrease. Transactions may only be included in blocks with an<br class="">
indentical vote, thus providing miners with a monetary incentive via<br class="">
fees to vote according to user wishes.<br class="">
<br class="">
Of course, to cast a "don't care" vote we can either define an<br class="">
additional bit, or sign the transaction with both versions. Equally we<br class="">
can even have different versions with different fees, broadcast via a<br class="">
mechanism such as replace-by-fee.<br class="">
<br class="">
<br class="">
See also John Dillon's proposal for proof-of-stake blocksize voting:<br class="">
<br class="">
<a href="https://www.mail-archive.com/bitcoin-development@lists.sourceforge.net/msg02323.html" rel="noreferrer" target="_blank" class="">https://www.mail-archive.com/bitcoin-development@lists.sourceforge.net/msg02323.html</a><br class="">
<span class="HOEnZb"><font color="#888888" class=""><br class="">
--<br class="">
'peter'[:-1]@<a href="http://petertodd.org/" rel="noreferrer" target="_blank" class="">petertodd.org</a><br class="">
0000000000000000127ab1d576dc851f374424f1269c4700ccaba2c42d97e778<br class="">
</font></span><br class="">------------------------------------------------------------------------------<br class="">
<br class="">_______________________________________________<br class="">
Bitcoin-development mailing list<br class="">
<a href="mailto:Bitcoin-development@lists.sourceforge.net" class="">Bitcoin-development@lists.sourceforge.net</a><br class="">
<a href="https://lists.sourceforge.net/lists/listinfo/bitcoin-development" rel="noreferrer" target="_blank" class="">https://lists.sourceforge.net/lists/listinfo/bitcoin-development</a><br class="">
<br class=""></blockquote></div><br class=""></div>
------------------------------------------------------------------------------<br class="">_______________________________________________<br class="">Bitcoin-development mailing list<br class=""><a href="mailto:Bitcoin-development@lists.sourceforge.net" class="">Bitcoin-development@lists.sourceforge.net</a><br class="">https://lists.sourceforge.net/lists/listinfo/bitcoin-development<br class=""></div></blockquote></div><br class=""></div></div></body></html>