public final class CryptoBatch

Many signature verifications or hashes in one call: the deposits of a block an exchange scans, the transactions an indexer checks, the leaves of a Merkle tree.

Where the platform has native kernels the whole batch crosses into native code once and is spread over every CPU core, so a batch of thousands runs several times faster than the same calls one at a time. Elsewhere it is the same loop over Secp256k1.verify, Schnorr.verify, Ed25519.verify or Hash that a caller would write.

Every entry gets exactly the answer the single call gives it; nothing here uses a batch equation that could accept a signature a single verify rejects. A malformed entry – a null, a key that does not parse, a wrong length – is simply invalid, so one bad entry never aborts the rest.

Every method has an asynchronous form, named with Async and taking a Callback, which runs the same batch off the calling thread. In the app the callback runs on the EDT, so a screen can start a batch and show its result without blocking; in a backend it runs on the thread that did the work. In a browser the asynchronous forms are the ones to use: there a large batch goes to the GPU through WebGPU, which answers only asynchronously, and the synchronous form holds its thread for that long. The arguments are checked before the call returns, so a malformed batch throws right away rather than reaching the callback. The batch reads the arrays it was given, not a copy, so they belong to it until the callback runs: changing one before then changes the entries being verified. The callback runs exactly once, with the result or with whatever was thrown, an Error included.