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:36

This is also why we don't want the caller to have to chunk up the batch for GPUs, and why we do not want a distinct call for CPU or GPU. We arrange the data in an optimal form for either, and expect the call to always complete. There is not even any memory allocation required to execute the call (we don't allocate any when we invoke on the secp loop), so not even OOM should be a possible failure condition.