What are compute mass and storage mass in Kaspa transactions?

Since KIP9, every Kaspa transaction carries two separate 'mass' values — compute mass and storage mass — that together cap how much work each block can demand from the network. Compute mass limits how much processing each block requires from nodes, while storage mass limits how much data a block can permanently add to the blockchain's record. Think of them as two separate governors: one watches CPU load, the other watches long-term disk use. Knowing these limits exist helps beginners understand that Kaspa has built-in safeguards so no single block can quietly overwhelm the nodes that keep the network running.