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

josie18:11

What would we do with an error from a math function?

if a function with preconditions satisfied cannot satisfy its postconditions, it should throw an exception. since we can't throw an exception across a library boundary, it should translate to an error code. libbitcoin can then decide what to do, which in this case id argue execute a clean shutdown. it should not treat it as a consensus failure , which is not an error but a conclusion. in the case here, i was trying to get dynamic chunking working, ultrafast failed to acquire the memory it needed on the gpu and that was interpreted as the batch being consensus invalid by libbitcoin due to an array with all zeros

(edited)