Sep 28, 2026

I was referring to CPU batching. For unbatched (scalar) signature verification I haven't seen much differentiation. Ours is already withing 0-2% of libsecp256k1, which isn't even a measurable difference over a full validation, maybe just a tiny bit more CPU usage. But I don't control what dependencies people use. We'll definitely keep the support open. Some will want libsecp256k1 because they think it's more secure, and others will want ultrafast for better performance.