What new opcodes does Toccata add to Kaspa, and why do they matter?

Toccata introduces four groups of new transaction opcodes — KIP16, KIP17, KIP20, and KIP21 — that together let developers write complex logic directly into Kaspa's base layer. KIP16 enables zero-knowledge proof verification (a cryptographic technique for proving something is true without revealing the underlying data); KIP17 adds covenant programming (rules baked into how a UTXO — an unspent coin — can be spent); KIP20 adds covenant identifiers that track UTXO lineage across transactions; and KIP21 introduces a partitioned sequencing commitment scheme that makes ZK proving more computationally efficient. Before Toccata, achieving this kind of programmability on Kaspa required trusted intermediaries or centralized coordination. These changes matter because they open the door to trustless applications built directly on Kaspa's Layer 1, without relying on a third party to enforce the rules.