Bitcoin full node and query server

Jul 1, 2026

View in context in the libbitcoin Slack #general mirror.

josie11:30
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
Vano Chkheidze18:42
Agreed. We’ll align to that contract: libbitcoin should keep one secp-style verification call, with no CPU/GPU split and no caller-managed chunking or GPU recovery path. GPU will be treated as an internal engine accelerator. If it is unavailable or unsupported, the engine falls back to CPU. If the math cannot be completed, that is a fatal engine failure, not consensus invalid data.
👍 1👍🏻 1