Damus
Kevin Ravens₿erg ⚡️ ☁️ · 2w
I did a full verification IBD (GPU-accelerated) with latest libbitcoin build 🚀 in just ~3.9h limited by the read speed of my nvme. https://blossom.primal.net/60c30b1c84f41ad910c3fffcb2abb6501a3f131...
nostrich profile picture
Accelerating IBD with more intelligent UTXO pruning was the topic of "Accelerating IBD with SwiftSync" at this year's MIT Bitcoin Expo. TLDR...or maybe TLDW...you can get the correct final UTXO set from the network before starting (or compute it without checking sigs), and use that verify only the transactions that destroy UTXO's that never made it to the final set.

Select Day 1 (in the upper left drop-down) and jump to 42 minutes: https://mitbitcoinexpo.org/livestream

The PR on Bitcoin Core got a bit of resistance because it touches the code in so many places: https://github.com/bitcoin/bitcoin/pull/34004

In my experience, much like yours, even with a mere CPU, mass-storage I/O bottlenecks IBD.
1❤️1
Kevin Ravens₿erg ⚡️ ☁️ · 2w
Thanks, there are devs that worked on SwiftSync also helping out with Libbitcoin (by evoskuil). To find out what the limit is we can push IBD to on various hardware configurations, from small form factor PC to big servers.