Why does Kaspa's storage mass require full UTXO data to calculate?

Storage mass cannot be determined from the transaction bytes alone — it depends on the exact KAS value of every input being spent, and those values are only known by looking up the UTXOs (unspent outputs) that the transaction is consuming. Compute mass, by contrast, can be measured from the raw transaction structure without any extra context. Because every node in the network must agree on the same mass value, storage mass validation is a "populated transaction" step: the node must have full UTXO context loaded before it can complete the check. For anyone building on Kaspa, this means storage mass validation is inherently stateful and cannot be done in an offline or lightweight mode.