Jul 22, 2026

Completed a couple full validation runs using Ultrafast as a drop-in secp256k1 replacement (no GPU linkage). The straight inline validation run came it at +1 second vs. the baseline of 1.35 hrs, so these are equivalent. The batched CPU run came in at 1.65 hrs which I assume will also match the a baseline from secp256k1 (running now). While it would be nice if we got a CPU bump from UF, it's sufficient/excellent that we are seeing parity. This allows it to be set up as a dependency swap, as opposed to an additional dependency. And the GPU functionality can be incorporated into the statically-linked builds for use where GPU is available, with the engine dropping into CPU where not. However since full validation CPU batching is always slower than inline, this will remain an important configuration knob. The user or outer controller will have to termine whether it's worth turning on batching. If it's turned on and the GPU is slow, unsupported, or missing - UF will drop into CPU verification. But at least (in this worst case) the difference (20%) between batched and inline CPU is not huge.