From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1V9t41-000323-T1 for bitcoin-development@lists.sourceforge.net; Thu, 15 Aug 2013 08:37:49 +0000 X-ACL-Warn: Received: from vps7135.xlshosting.net ([178.18.90.41]) by sog-mx-4.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1V9t40-0005Vu-Nc for bitcoin-development@lists.sourceforge.net; Thu, 15 Aug 2013 08:37:49 +0000 Received: by vps7135.xlshosting.net (Postfix, from userid 1000) id 58CBC33C7FF; Thu, 15 Aug 2013 10:37:42 +0200 (CEST) Date: Thu, 15 Aug 2013 10:37:42 +0200 From: Pieter Wuille To: Mike Hearn Message-ID: <20130815083741.GA12713@vps7135.xlshosting.net> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-PGP-Key: http://sipa.ulyssis.org/pubkey.asc User-Agent: Mutt/1.5.21 (2010-09-15) X-Spam-Score: -1.6 (-) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (pieter.wuille[at]gmail.com) 0.0 DKIM_ADSP_CUSTOM_MED No valid author signature, adsp_override is CUSTOM_MED -2.8 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain 1.2 NML_ADSP_CUSTOM_MED ADSP custom_med hit, and not from a mailing list X-Headers-End: 1V9t40-0005Vu-Nc Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] Version 0.9 goals 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, 15 Aug 2013 08:37:50 -0000 On Thu, Aug 15, 2013 at 10:09:48AM +0200, Mike Hearn wrote: > Sounds awesome! > > Pieter told me at lunch that headers first cut sync time to 45 minutes for > him, which is another amazing improvement from the master of optimisations. Just to make sure nobody expects a magic bullet: this was on a hexacore Xeon CPU, with several GB of -dbcache, libsecp256k1 for verification, and a very good network connection. It is repeatable and from random network peers, though. The code is here: https://github.com/sipa/bitcoin/commits/headersfirst It's usable and seems to be stable (including reindexing, which needs support for block files with out-of-order blocks now), but I still want to clean some things up before pullreq'in. There are probably some heuristic tweaks possible as well - Gregory found that performance is reduced for the first part of the chain on high-latency networks. > Pieter, Matt and I also agreed that for maximum impact we should really try > to ship payment protocol support in at least two clients simultaneously and > ideally with a big merchant signed up too - to send a powerful message that > we really mean it. Someone volunteered last week to do it for bitcoinj and > if he doesn't pull through, I have some old code from EOY 2012 that I could > update to the latest spec and ship at least some basic support. I'd hope > that we can get Bitcoin Wallet or MultiBit updates out once bcj has support > pretty fast. > > Also, Jeff said that BitPay want to be a leader in support for the > protocol. So let's try and co-ordinate release dates so we can make a bit > of a splash and grab the ecosystems attention. I believe we do need some wider support than just Bitcoin-Qt, indeed, as the number of people actually using the reference client as a wallet is quite low now. Ideally, several clients and merchants start support for it in a short timeframe... -- Pieter