How does Kaspa's runtime sigop counting reduce transaction fees?

Kaspa now counts signature operations (sigops) only as they are actually executed in a transaction, instead of charging for every sigop found during a static pre-scan. Previously, the script engine scanned for `SigVerify` opcodes and charged the transaction for all of them — even opcodes that were never triggered during execution. That inflated the transaction's mass, which is the metric that drives fee calculations, so users were effectively billed for work the network never performed. By tallying only executed sigops, transaction mass shrinks and fees drop accordingly. For a beginner, this means Kaspa transactions — especially those using advanced script features like additive addresses — should cost less in fees without any action on your part.