Bitcoin full node and query server

Mar 5, 2024

View in context in the libbitcoin Slack #general mirror.

evoskuil16:07
After swapping out the simple std::unordered_map for a multiindex boost table I'm now able to maintain height-indexed requests with constant time hash-based indexing. This tracking is still very inefficient relative to where it will be soon (moving one pointer per channel) around vs. moving millions of records. But I've achieved full saturation of my network at ~940Mbps (peak determined by speedtest.net) as measured internally via block download tracking/logging and externally using a network monitor. I have no reason to believe this would not scale beyond my network capacity. At 940Mbps/8 = 117.5 MBps = 423GBph. I haven't measured the chain in a while, but that should be close to all of it.
🎉 3
evoskuil20:55
With that we achieve a much more highly indexed and performant query store than Core. Validation metadata will increase that somewhat, and then of course optional indexation such as all payment addresses. But validation metadata can be purged once current.
🙌 1