<oembed><type>rich</type><version>1.0</version><author_name>npub17qxssk9sj2r7jswvh3y32e7vwz7mcckhz33gk9nurdmw0lhsfkgswupwet</author_name><author_url>https://nostr.ae/npub17qxssk9sj2r7jswvh3y32e7vwz7mcckhz33gk9nurdmw0lhsfkgswupwet</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2015-06-12&#xA;📝 Original message:On Friday, 12 June 2015, at 7:34 pm, Peter Todd wrote:&#xA;&gt; On Fri, Jun 12, 2015 at 02:22:36PM -0400, Matt Whitlock wrote:&#xA;&gt; &gt; Why should miners only be able to vote for &#34;double the limit&#34; or &#34;halve&#34; the limit? If you&#39;re going to use bits, I think you need to use two bits:&#xA;&gt; &gt; &#xA;&gt; &gt; &#x9;0 0 = no preference (&#34;wildcard&#34; vote)&#xA;&gt; &gt; &#x9;0 1 = vote for the limit to remain the same&#xA;&gt; &gt; &#x9;1 0 = vote for the limit to be halved&#xA;&gt; &gt; &#x9;1 1 = vote for the limit to be doubled&#xA;&gt; &gt; &#xA;&gt; &gt; User transactions would follow the same usage. In particular, a user vote of &#34;0 0&#34; (no preference) could be included in a block casting any vote, but a block voting &#34;0 0&#34; (no preference) could only contain transactions voting &#34;0 0&#34; as well.&#xA;&gt; &#xA;&gt; Sounds like a good encoding to me. Taking the median of the three&#xA;&gt; options, and throwing away &#34;don&#39;t care&#34; votes entirely, makes sense.&#xA;&#xA;I hope you mean the *plurality* of the three options after throwing away the &#34;don&#39;t cares,&#34; not the *median*.</html></oembed>