When does storage mass start raising Kaspa transaction fees?

Storage mass only becomes the dominant fee factor in Kaspa when the inputs being spent are relatively small — and the exact threshold at which it takes over is inversely proportional to the total value of the transaction. Kaspa's fee model derives a total mass from two components: compute mass (based on the complexity of verifying signatures) and storage mass (based on how the sizes of outputs compare to inputs). For large inputs, storage mass stays well below compute mass and has no practical effect. For small inputs, storage mass grows and can push the overall fee higher than compute mass alone would. This matters because it means fee surprises are most likely to hit users who are spending many small UTXOs — tiny amounts left over as change or received as micropayments.