📅 Original date posted:2013-08-15
📝 Original message: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
Pieter Wuille [ARCHIVE] /
npub1tj…jtl6r
2023-06-07 15:05:56
in reply to nevent1q…uhkc
Author Public Key
npub1tjephawh7fdf6358jufuh5eyxwauzrjqa7qn50pglee4tayc2ntqcjtl6rSeen on
wss://relay.noswhere.comPublished at
2023-06-07 15:05:56Event JSON
{
"id": "19ddbac10a71d3f76c85e79bf736b01ccf8f84b5e6b5bdf77cc15c5bb32b6d67",
"pubkey": "5cb21bf5d7f25a9d46879713cbd32433bbc10e40ef813a3c28fe7355f49854d6",
"created_at": 1686150356,
"kind": 1,
"tags": [
[
"e",
"16b0b3d093d3a082b4a61ae828e9ba30a8cab43b8fbd091391c9e49588991dc7",
"",
"root"
],
[
"e",
"48e139c112efe7ae57ea9b13bb95f5b92696f312e4ccaaf7c167465b16eaca28",
"",
"reply"
],
[
"p",
"eb7ca795057ca7cabde6f541c741e661d013414934e5934c2e04c6677625c99a"
]
],
"content": "📅 Original date posted:2013-08-15\n📝 Original message:On Thu, Aug 15, 2013 at 10:09:48AM +0200, Mike Hearn wrote:\n\u003e Sounds awesome!\n\u003e \n\u003e Pieter told me at lunch that headers first cut sync time to 45 minutes for\n\u003e him, which is another amazing improvement from the master of optimisations.\n\nJust to make sure nobody expects a magic bullet: this was on a hexacore Xeon\nCPU, with several GB of -dbcache, libsecp256k1 for verification, and a very good\nnetwork connection. It is repeatable and from random network peers, though. The\ncode is here:\n\n https://github.com/sipa/bitcoin/commits/headersfirst\n\nIt's usable and seems to be stable (including reindexing, which needs support for\nblock files with out-of-order blocks now), but I still want to clean some\nthings up before pullreq'in. There are probably some heuristic tweaks\npossible as well - Gregory found that performance is reduced for the first\npart of the chain on high-latency networks.\n\n\u003e Pieter, Matt and I also agreed that for maximum impact we should really try\n\u003e to ship payment protocol support in at least two clients simultaneously and\n\u003e ideally with a big merchant signed up too - to send a powerful message that\n\u003e we really mean it. Someone volunteered last week to do it for bitcoinj and\n\u003e if he doesn't pull through, I have some old code from EOY 2012 that I could\n\u003e update to the latest spec and ship at least some basic support. I'd hope\n\u003e that we can get Bitcoin Wallet or MultiBit updates out once bcj has support\n\u003e pretty fast.\n\u003e \n\u003e Also, Jeff said that BitPay want to be a leader in support for the\n\u003e protocol. So let's try and co-ordinate release dates so we can make a bit\n\u003e of a splash and grab the ecosystems attention.\n\nI believe we do need some wider support than just Bitcoin-Qt, indeed, as\nthe number of people actually using the reference client as a wallet is\nquite low now. Ideally, several clients and merchants start support for it\nin a short timeframe...\n\n-- \nPieter",
"sig": "48a969116d2ca0355b64a70495f2949f62271b014725b48cfada609cb7f041c539d57674aefe312cdd5fed32464d17f1dbe800b582e5b5bd15113c826b6a45a5"
}