Bitcoin full node and query server

Jul 1, 2026

View in context in the libbitcoin Slack #general mirror.

nice work regarding the vert tables! was also starting to suspect it was increasing io. i went down a different route with my benching and tried to understand the ultrafast internals a bit better. i came up with a few patches ive been running that have shown measurable improvements. namely, i want to move anything that can be considered sig verification to the GPU, i.e., no CPU marshalling batches and instead columns are streamed directly into reusable GPU buffers, verified on device, and copied back. i dont think we can ever truly get zero copy since we have to cross a device memory boundary. but if that is possible and the goal, i think this at least is a good step toward it anyways. @Vano Chkheidze you can see the patches i am using here: github.com/josibake/…/patches

evoskuil18:32

The design objective was of course not to pass GPU failures as invalids. And we could of course abort if the math cannot be completed. There is really no rational execution path at that point. If we cannot do the math, the process needs to terminate, just as I would expect it to do if we cannot do simple addition. The secp library isn't a GPU library, it's a math library. The GPU is one of the tools that it has available. If no GPU can be used, it should fall back to CPU verification. Because if it doesn't that is specifically what the caller is going to have to do. When we call libsecp256k1 we don't have any failure mode, this should not be any different.