How does Kaspa calculate transaction fees for ZK proof verification?

Kaspa prices ZK proof verification by measuring how many times slower it is than a standard ECDSA signature check, then using that ratio as a fee multiplier. Benchmarks run over one thousand iterations on representative hardware produced the following averages: ECDSA completed in about 12.3 microseconds, Groth16 proof verification took about 1.65 milliseconds (roughly 134 times slower than ECDSA), and STARK proof verification took about 9.1 milliseconds (roughly 738 times slower). These ratios map directly to signature operation unit costs in the fee model, so a transaction requiring STARK verification carries a cost multiplier roughly 738 times that of a single signature. Knowing this helps developers and users anticipate how much more expensive ZK-proof transactions are compared to ordinary Kaspa transfers.