What is transient_storage_mass in Kaspa?

transient_storage_mass is a new type of computational weight Kaspa assigns to each transaction based on how many bytes it takes up when serialized. Each byte of transaction data is multiplied by 4 to produce the transaction's transient_storage_mass, and the total across all transactions in a block cannot exceed the block's mass budget of 500,000 units — which works out to a 125KB block-size ceiling. The multiplier of 4 is not arbitrary: it comes from dividing the 500,000-mass block budget by the 125,000-byte target (500,000 ÷ 125,000 = 4 mass per byte). For a beginner, this matters because it is the mechanism Kaspa uses at the consensus layer to prevent any single block from growing so large that it strains the network.