Bitcoin full node and query server

Feb 17, 2025

View in context in the libbitcoin Slack #general mirror.

evoskuil04:51
Notice that the new validate was tracking above (slower) then the previous. That's because most of the cost of confirm has been moved to validate. This of course delays confirmations, but they are much faster as a result, so they catch up, and the result is about the same. What the design change means is that with more resources, confirmation can scale almost as well as validation. The point table is currently 136GiB, due to consolidation with the parts of the spend table removed from the spend index - to speed up the spender queries. I believe that was the main reason that the entire thing got about 50% slower. However this change has restored the original best performance, which basically tracks signature verifications. Once I split the point table out again it will be reduced to 86GiB, which should further reduce confirmation paging and therefore query cost. Hopefully that will help with the mini.