Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from <jgarzik@bitpay.com>) id 1YgDou-0005Ux-K9 for bitcoin-development@lists.sourceforge.net; Thu, 09 Apr 2015 14:52:40 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of bitpay.com designates 209.85.214.178 as permitted sender) client-ip=209.85.214.178; envelope-from=jgarzik@bitpay.com; helo=mail-ob0-f178.google.com; Received: from mail-ob0-f178.google.com ([209.85.214.178]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1YgDot-0000wG-Hq for bitcoin-development@lists.sourceforge.net; Thu, 09 Apr 2015 14:52:40 +0000 Received: by obbry2 with SMTP id ry2so17452538obb.1 for <bitcoin-development@lists.sourceforge.net>; Thu, 09 Apr 2015 07:52:34 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=bQXUgaM550bS0WYqlvD4zWx0HZL20s/ApfeAGE4M96A=; b=jPOjVP8NBSrbZZGW0kj9usQo8+/YOWf7PPogQT49Nn+70c31dVL60EFCDh3B26VW1v JOHCv+3F8XjJ2/eqVFigkZCDdEonRebmDssK8JiCozlIEHoKu/ajAiky6A3Ge5sXjvgN TuZ2yQfHrjae1oTcTrx6VD3+GAac9zEWc5Ki5R/3mzNE6DFrDQFU1cNUMB0BXTgrUxgk 1OccViEoeLBRpCgmRFM/1fUEn70OXnpSGPs67u2hdWUrXb37P/wgFwSEBD3oOqtFZA/n Aa2d/gZlaeL1V8nUuhahuTMm2r67o2Ws0ncslxb7yT9uZZH5cxg1CSH0OWNQuUuCEXqf ur0g== X-Gm-Message-State: ALoCoQm08nyt58q8jrj0bY8HaFMsJM1wL54aF/6OaWThkvOHox8jSQufbb40D0Mg56jAH45pF75C X-Received: by 10.182.24.133 with SMTP id u5mr39018071obf.27.1428589392250; Thu, 09 Apr 2015 07:23:12 -0700 (PDT) MIME-Version: 1.0 Received: by 10.202.132.1 with HTTP; Thu, 9 Apr 2015 07:22:52 -0700 (PDT) In-Reply-To: <CABHVRKSET18D13+yi4MTPs6+4xwUD5vuJszCOJG9CaTi0+CAvA@mail.gmail.com> References: <CABHVRKTNFoLm9LEO=ctT_UP9zW7QOMQzVXitKC=PAzj=HG9OHg@mail.gmail.com> <CANEZrP12kZ8vRAo=feprJ9_oRXUPKJ=iF6kZdxxbai=TxjzM9g@mail.gmail.com> <CABHVRKSET18D13+yi4MTPs6+4xwUD5vuJszCOJG9CaTi0+CAvA@mail.gmail.com> From: Jeff Garzik <jgarzik@bitpay.com> Date: Thu, 9 Apr 2015 07:22:52 -0700 Message-ID: <CAJHLa0NgV=6D=TAy4sm_EAfYiZULK-d9GMcddW1-DZRHCE8Sew@mail.gmail.com> To: Stephen Morse <stephencalebmorse@gmail.com> Content-Type: multipart/alternative; boundary=001a11c308644162d105134b6330 X-Spam-Score: -0.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 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message -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: 1YgDot-0000wG-Hq Cc: bitcoin-development <bitcoin-development@lists.sourceforge.net> Subject: Re: [Bitcoin-development] Build your own nHashType X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: <bitcoin-development.lists.sourceforge.net> List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, <mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe> List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development> List-Post: <mailto:bitcoin-development@lists.sourceforge.net> List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help> List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, <mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe> X-List-Received-Date: Thu, 09 Apr 2015 14:52:40 -0000 --001a11c308644162d105134b6330 Content-Type: text/plain; charset=UTF-8 On Thu, Apr 9, 2015 at 7:10 AM, Stephen Morse <stephencalebmorse@gmail.com> wrote: > Is hashing transaction data once for each input really a huge bottleneck, > though? Do mobile devices have an issue with this? > Think about what slow transaction verification speed means. Slower propagation across the network. More work per node. Greater opportunity for algorithmic attacks, races and other shenanigans by attackers. -- Jeff Garzik Bitcoin core developer and open source evangelist BitPay, Inc. https://bitpay.com/ --001a11c308644162d105134b6330 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">On Thu, Apr 9, 2015 at 7:10 AM, Stephen Morse <span dir=3D= "ltr"><<a href=3D"mailto:stephencalebmorse@gmail.com" target=3D"_blank">= stephencalebmorse@gmail.com</a>></span> wrote:<br><div class=3D"gmail_ex= tra"><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"= margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"= ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><div>Is hashing = transaction data once for each input really a huge bottleneck, though? Do m= obile devices have an issue with this?</div><div></div></div></div></div></= blockquote></div><div class=3D"gmail_extra"><br></div><div class=3D"gmail_e= xtra"><br></div>Think about what slow transaction verification speed means.= =C2=A0 Slower propagation across the network.=C2=A0 More work per node.=C2= =A0 Greater opportunity for algorithmic attacks, races and other shenanigan= s by attackers.<br><br>-- <br><div class=3D"gmail_signature">Jeff Garzik<br= >Bitcoin core developer and open source evangelist<br>BitPay, Inc. =C2=A0 = =C2=A0 =C2=A0<a href=3D"https://bitpay.com/" target=3D"_blank">https://bitp= ay.com/</a></div> </div></div> --001a11c308644162d105134b6330--