Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Z3U4F-0006tr-J3 for bitcoin-development@lists.sourceforge.net; Fri, 12 Jun 2015 18:52:39 +0000 X-ACL-Warn: Received: from resqmta-po-09v.sys.comcast.net ([96.114.154.168]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:AES128-SHA:128) (Exim 4.76) id 1Z3U4E-0006Ed-SY for bitcoin-development@lists.sourceforge.net; Fri, 12 Jun 2015 18:52:39 +0000 Received: from resomta-po-03v.sys.comcast.net ([96.114.154.227]) by resqmta-po-09v.sys.comcast.net with comcast id fWrd1q0064ueUHc01WsZb2; Fri, 12 Jun 2015 18:52:33 +0000 Received: from crushinator.localnet ([IPv6:2601:186:c000:825e:e9f4:8901:87c7:24a0]) by resomta-po-03v.sys.comcast.net with comcast id fWsY1q0064eLRLv01WsYW6; Fri, 12 Jun 2015 18:52:33 +0000 From: Matt Whitlock To: Peter Todd Date: Fri, 12 Jun 2015 14:52:31 -0400 Message-ID: <3371959.rhW3Li6WRR@crushinator> User-Agent: KMail/4.14.9 (Linux/3.18.12-gentoo; KDE/4.14.9; x86_64; ; ) In-Reply-To: <20150612184450.GG19199@muck> References: <20150612181153.GB19199@muck> <3287607.HcH18TyfSu@crushinator> <20150612184450.GG19199@muck> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" X-Spam-Score: 0.0 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no trust [96.114.154.168 listed in list.dnswl.org] 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1Z3U4E-0006Ed-SY Cc: bitcoin-development@lists.sourceforge.net Subject: Re: [Bitcoin-development] User vote in blocksize through fees X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Jun 2015 18:52:39 -0000 On Friday, 12 June 2015, at 7:44 pm, Peter Todd wrote: > On Fri, Jun 12, 2015 at 02:36:31PM -0400, Matt Whitlock wrote: > > On Friday, 12 June 2015, at 7:34 pm, Peter Todd wrote: > > > 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" o= r "halve" the limit? If you're going to use bits, I think you need to u= se two bits: > > > >=20 > > > > =090 0 =3D no preference ("wildcard" vote) > > > > =090 1 =3D vote for the limit to remain the same > > > > =091 0 =3D vote for the limit to be halved > > > > =091 1 =3D vote for the limit to be doubled > > > >=20 > > > > User transactions would follow the same usage. In particular, a= user vote of "0 0" (no preference) could be included in a block castin= g any vote, but a block voting "0 0" (no preference) could only contain= transactions voting "0 0" as well. > > >=20 > > > Sounds like a good encoding to me. Taking the median of the three= > > > options, and throwing away "don't care" votes entirely, makes sen= se. > >=20 > > I hope you mean the *plurality* of the three options after throwing= away the "don't cares," not the *median*. >=20 > Median ensures that voting "no change" is meaningful. If "double" + "= no > change" =3D 66%-1, you'd expect the result to be "no change", not "ha= lve"" > With a plurality vote you'd end up with a halving that was supported = by > a minority. I'm very confused. Let's say, out of the 12,000 blocks in a voting period: =E2=80=A2 1000 blocks express no preference, =E2=80=A2 2000 blocks vote to halve the limit, =E2=80=A2 3500 blocks vote to double the limit, and =E2=80=A2 5500 blocks vote to keep the limit the same. The plurality vote is to keep the limit the same. The median vote is=E2= =80=A6 well, I'm not sure, since there are four choices, and an average= of the two "middle" choices doesn't seem to make sense.