From: Pieter Wuille <pieter.wuille@gmail.com>
To: Mike Hearn <mike@plan99.net>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Version 0.9 goals
Date: Thu, 15 Aug 2013 10:37:42 +0200 [thread overview]
Message-ID: <20130815083741.GA12713@vps7135.xlshosting.net> (raw)
In-Reply-To: <CANEZrP3bt40ThBcqWLfzuS5508mpbo4Z5qxh9AJs-FRrk0QJsA@mail.gmail.com>
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
next prev parent reply other threads:[~2013-08-15 8:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-15 0:29 [Bitcoin-development] Version 0.9 goals Gavin Andresen
2013-08-15 8:09 ` Mike Hearn
2013-08-15 8:22 ` slush
2013-08-15 9:02 ` Mike Hearn
2013-08-15 14:32 ` slush
2013-08-15 15:22 ` Mike Hearn
2013-08-15 8:37 ` Pieter Wuille [this message]
2013-08-15 21:12 ` Wendell
2013-08-15 10:12 ` Melvin Carvalho
2013-08-15 10:49 ` Wladimir
2013-08-15 10:56 ` Pieter Wuille
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130815083741.GA12713@vps7135.xlshosting.net \
--to=pieter.wuille@gmail.com \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=mike@plan99.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox