Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1YxmG5-0001xW-2V for bitcoin-development@lists.sourceforge.net; Thu, 28 May 2015 01:05:17 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.220.52 as permitted sender) client-ip=209.85.220.52; envelope-from=patrick.strateman@gmail.com; helo=mail-pa0-f52.google.com; Received: from mail-pa0-f52.google.com ([209.85.220.52]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1YxmG4-0001jO-2g for bitcoin-development@lists.sourceforge.net; Thu, 28 May 2015 01:05:17 +0000 Received: by padbw4 with SMTP id bw4so10437910pad.0 for ; Wed, 27 May 2015 18:05:10 -0700 (PDT) X-Received: by 10.70.96.194 with SMTP id du2mr382899pdb.108.1432775110345; Wed, 27 May 2015 18:05:10 -0700 (PDT) Received: from [10.45.134.9] (c-24-5-81-164.hsd1.ca.comcast.net. [24.5.81.164]) by mx.google.com with ESMTPSA id f1sm380840pds.62.2015.05.27.18.05.09 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 27 May 2015 18:05:09 -0700 (PDT) Message-ID: <556669C4.50406@gmail.com> Date: Wed, 27 May 2015 18:05:08 -0700 From: Patrick Strateman User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.7.0 MIME-Version: 1.0 To: bitcoin-development@lists.sourceforge.net References: <201505270346.17014.luke@dashjr.org> <20150527101516.GB25814@savin.petertodd.org> <55664AA2.7020206@certimix.com> In-Reply-To: <55664AA2.7020206@certimix.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable X-Spam-Score: -1.6 (-) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (patrick.strateman[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 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: 1YxmG4-0001jO-2g Subject: Re: [Bitcoin-development] Version bits proposal 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: Thu, 28 May 2015 01:05:17 -0000 There is absolutely no reason to do this. Any reasonable micro-controller can build merkle tree roots significantly faster than is necessary. 1 Th/s walks the nonce range once every 4.3ms. The largest valid merkle trees are 14 nodes high. That translates to 28 SHA256 ops per 4.3ms or 6511 SHA256 ops/second. For reference an RPi 1 model B does 2451050 SHA256 ops/second. On 05/27/2015 03:52 PM, Sergio Lerner wrote: > I like the idea but I think we should leave at least 16 bits of the > version fixed as an extra-nonce. > If we don't then miners may use them as a nonce anyway, and mess with > the soft-fork voting system. > My original proposal was this: https://github.com/bitcoin/bitcoin/pull/= 5102 > > Best regards > > > -----------------------------------------------------------------------= ------- > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development