📅 Original date posted:2014-10-12
📝 Original message:This is great Pieter. I was able to sync the entire blockchain from
scratch in a little over 4 hours on a laptop over cable modem. :) No
issues to report. Even my family photos are intact! This makes it
practical to run a full node, part time on a laptop again.
Aaron Voisine
breadwallet.com
On Sat, Oct 11, 2014 at 4:34 PM, Pieter Wuille <pieter.wuille at gmail.com> wrote:
> Hi all,
>
> I believe that a large change that I've been working on for Bitcoin
> Core is ready for review and testing: headers-first synchronization.
> In short, it changes the way the best chain is discovered, downloaded
> and verified, with several advantages:
> * Parallel block downloading (much faster sync on typical network connections).
> * No more stalled downloads.
> * Much more robust against unresponsive or slow peers.
> * Removes a class of DoS attacks related to peers feeding you
> low-difficulty valid large blocks on a side branch.
> * Reduces the need for checkpoints in the code.
> * No orphan blocks stored in memory anymore (reducing memory usage during sync).
> * A major step step towards an SPV mode using the reference codebase.
>
> Historically, this mode of operation has been known for years (Greg
> Maxwell wrote up a description of a very similar method in
> https://en.bitcoin.it/wiki/User:Gmaxwell/Reverse_header-fetching_sync
> in early 2012, but it was known before that), but it took a long time
> to refactor these code enough to support it.
>
> Technically, it works by replacing the single-peer blocks download by
> a single-peer headers download (which typically takes seconds/minutes)
> and verification, and simultaneously fetching blocks along the best
> known headers chain from all peers that are known to have the relevant
> blocks. Downloading is constrained to a moving window to avoid
> unbounded unordering of blocks on disk (which would interfere with
> pruning later).
>
> At the protocol level, it increases the minimally supported version
> for peers to 31800 (corresponding to bitcoin v3.18, released in
> december 2010), as earlier versions did not support the getheaders P2P
> message.
>
> So, the code is available as a github pull request
> (https://github.com/bitcoin/bitcoin/pull/4468), or packaged on
> http://bitcoin.sipa.be/builds/headersfirst, where you can also find
> binaries to test with.
>
> Known issues:
> * At the very start of the sync, especially before all headers are
> processed, downloading is very slow due to a limited number of blocks
> that are requested per peer simultaneously. The policies around this
> will need some experimentation can certainly be improved.
> * Blocks will be stored on disk out of order (in the order they are
> received, really), which makes it incompatible with some tools or
> other programs. Reindexing using earlier versions will also not work
> anymore as a result of this.
> * The block index database will now hold headers for which no block is
> stored on disk, which earlier versions won't support. If you are fully
> synced, it may still be possible to go back to an earlier version.
>
> Unknown issues:
> * Who knows, maybe it will replace your familiy pictures with Nyan
> Cat? Use at your own risk.
>
> TL;DR: Review/test https://github.com/bitcoin/bitcoin/pull/4468 or
> http://bitcoin.sipa.be/builds/headersfirst.
>
> --
> Pieter
>
> ------------------------------------------------------------------------------
> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
> http://p.sf.net/sfu/Zoho
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
Aaron Voisine [ARCHIVE] /
npub18g…knkzl
2023-06-07 15:26:22
in reply to nevent1q…gnsv
Author Public Key
npub18gjvug29c4yg46lmplq38e75gg6wn5mn8taytckcsr4jt8p74h3s5knkzlPublished at
2023-06-07 15:26:22Event JSON
{
"id": "be3007a20770e79f83bc018d16cf774b81d88a523eeaf664b4da014ec63bf130",
"pubkey": "3a24ce2145c5488aebfb0fc113e7d44234e9d3733afa45e2d880eb259c3eade3",
"created_at": 1686151582,
"kind": 1,
"tags": [
[
"e",
"18edb7eb4d79984cbabd2cd9a1902fcdfb0cb1646bb17e5ae6871fecf76a5cf2",
"",
"root"
],
[
"e",
"9e8baacedc66e3542bb9c2e83a55472157f607d69abd4db86562e3141a18ccd6",
"",
"reply"
],
[
"p",
"5cb21bf5d7f25a9d46879713cbd32433bbc10e40ef813a3c28fe7355f49854d6"
]
],
"content": "📅 Original date posted:2014-10-12\n📝 Original message:This is great Pieter. I was able to sync the entire blockchain from\nscratch in a little over 4 hours on a laptop over cable modem. :) No\nissues to report. Even my family photos are intact! This makes it\npractical to run a full node, part time on a laptop again.\n\nAaron Voisine\nbreadwallet.com\n\n\nOn Sat, Oct 11, 2014 at 4:34 PM, Pieter Wuille \u003cpieter.wuille at gmail.com\u003e wrote:\n\u003e Hi all,\n\u003e\n\u003e I believe that a large change that I've been working on for Bitcoin\n\u003e Core is ready for review and testing: headers-first synchronization.\n\u003e In short, it changes the way the best chain is discovered, downloaded\n\u003e and verified, with several advantages:\n\u003e * Parallel block downloading (much faster sync on typical network connections).\n\u003e * No more stalled downloads.\n\u003e * Much more robust against unresponsive or slow peers.\n\u003e * Removes a class of DoS attacks related to peers feeding you\n\u003e low-difficulty valid large blocks on a side branch.\n\u003e * Reduces the need for checkpoints in the code.\n\u003e * No orphan blocks stored in memory anymore (reducing memory usage during sync).\n\u003e * A major step step towards an SPV mode using the reference codebase.\n\u003e\n\u003e Historically, this mode of operation has been known for years (Greg\n\u003e Maxwell wrote up a description of a very similar method in\n\u003e https://en.bitcoin.it/wiki/User:Gmaxwell/Reverse_header-fetching_sync\n\u003e in early 2012, but it was known before that), but it took a long time\n\u003e to refactor these code enough to support it.\n\u003e\n\u003e Technically, it works by replacing the single-peer blocks download by\n\u003e a single-peer headers download (which typically takes seconds/minutes)\n\u003e and verification, and simultaneously fetching blocks along the best\n\u003e known headers chain from all peers that are known to have the relevant\n\u003e blocks. Downloading is constrained to a moving window to avoid\n\u003e unbounded unordering of blocks on disk (which would interfere with\n\u003e pruning later).\n\u003e\n\u003e At the protocol level, it increases the minimally supported version\n\u003e for peers to 31800 (corresponding to bitcoin v3.18, released in\n\u003e december 2010), as earlier versions did not support the getheaders P2P\n\u003e message.\n\u003e\n\u003e So, the code is available as a github pull request\n\u003e (https://github.com/bitcoin/bitcoin/pull/4468), or packaged on\n\u003e http://bitcoin.sipa.be/builds/headersfirst, where you can also find\n\u003e binaries to test with.\n\u003e\n\u003e Known issues:\n\u003e * At the very start of the sync, especially before all headers are\n\u003e processed, downloading is very slow due to a limited number of blocks\n\u003e that are requested per peer simultaneously. The policies around this\n\u003e will need some experimentation can certainly be improved.\n\u003e * Blocks will be stored on disk out of order (in the order they are\n\u003e received, really), which makes it incompatible with some tools or\n\u003e other programs. Reindexing using earlier versions will also not work\n\u003e anymore as a result of this.\n\u003e * The block index database will now hold headers for which no block is\n\u003e stored on disk, which earlier versions won't support. If you are fully\n\u003e synced, it may still be possible to go back to an earlier version.\n\u003e\n\u003e Unknown issues:\n\u003e * Who knows, maybe it will replace your familiy pictures with Nyan\n\u003e Cat? Use at your own risk.\n\u003e\n\u003e TL;DR: Review/test https://github.com/bitcoin/bitcoin/pull/4468 or\n\u003e http://bitcoin.sipa.be/builds/headersfirst.\n\u003e\n\u003e --\n\u003e Pieter\n\u003e\n\u003e ------------------------------------------------------------------------------\n\u003e Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer\n\u003e Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports\n\u003e Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper\n\u003e Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer\n\u003e http://p.sf.net/sfu/Zoho\n\u003e _______________________________________________\n\u003e Bitcoin-development mailing list\n\u003e Bitcoin-development at lists.sourceforge.net\n\u003e https://lists.sourceforge.net/lists/listinfo/bitcoin-development",
"sig": "44dfad4a378294f0e78488b3bb4d14485f247ee8a5d0ce4bf883781703e19a4a286b69c037cd3e8ad3ff1cd0f52f1f509416e3e7284e83975f51f44c7d71bedf"
}