Will the storageMass rename in Kaspa's Toccata release break existing integrations?

No — Kaspa's Toccata release includes a backward-compatibility bridge so existing integrations keep working while developers migrate. In JSON RPC transaction objects, both the old 'mass' field and the new 'storageMass' field are currently emitted with the same value, so code that reads 'mass' still gets correct data. In JavaScript and WASM transaction objects, 'mass' is deprecated but still works as an alias for 'storageMass'. The guidance for anyone building a new integration is to read and write 'storageMass' (or 'storage_mass' in Rust and protobuf) going forward. This matters because it means the network is giving developers a transition window rather than forcing an immediate breaking change, but the clock is ticking — new code should use the new field name now.