Jun 13, 2026

I didn't get a complete measure of performance, since the run was interrupted at around 700k for the above issue, and then I completed from that point. Up to that point the run as around 150% of the secp256k1 time, which is not surprising given that @Vano Chkheidze has said the Windows builds aren't optimized. And the NuGet package may not be optimal either. But it at least gets the toolchain moving for signature batching and silent payment search.