# Libbitcoin for Core people

**URL:** <https://delvingbitcoin.org/t/libbitcoin-for-core-people/1222>\
**Category:** Implementation\
**Tags:** libbitcoin\
**Created:** [October 28, 2024, 7:09pm UTC](https://delvingbitcoin.org/t/libbitcoin-for-core-people/1222 "2024-10-28T19:09:55Z")\
**Posts on this page:** 1\
**Showing post:** 35

<div class="post-metadata">

**Author:** ![andrewtoth](https://delvingbitcoin.org/user_avatar/delvingbitcoin.org/andrewtoth/32/576_2.png) [@andrewtoth](https://delvingbitcoin.org/u/andrewtoth)\
**Post date:** [December 2, 2024, 8:32pm UTC](https://delvingbitcoin.org/t/libbitcoin-for-core-people/1222/35 "2024-12-02T20:32:46Z")

</div>

Yes, and I believe any check that requires total or partial order is skipped if below the milestone block. This is what allows a sync in an hour. So, I think it’s still accurate to say that not looking up input prevouts is where the main speedup is.

Looking at a flamegraph of Bitcoin Core IBD, the majority of time is spent looking up input prevouts. That’s why parallelizing that provides a nice speedup. Skipping it entirely though is not possible since we would not have a utxo set at the end, which is not a constraint that libbitcoin has.

---

_[View the full topic](https://delvingbitcoin.org/t/libbitcoin-for-core-people/1222)._
