How much cheaper is Groth16 proof verification than STARK on Kaspa?

On Kaspa, Groth16 proof verification is roughly 5.5 times cheaper than STARK proof verification in computational cost terms. Benchmarks show Groth16 averages about 1.65 milliseconds to verify while STARK averages about 9.1 milliseconds — meaning Groth16 is around 134 times slower than a standard ECDSA signature, while STARK is around 738 times slower. Because Kaspa's fee model uses these ratios as direct cost multipliers, a transaction that uses Groth16 proofs will be significantly less expensive than one that uses STARK proofs for the same underlying computation. For developers building ZK-powered features on Kaspa, this trade-off between proof type and transaction cost is an important design decision.