What did the Kaspa TN-11 hard fork introduce?

The TN-11 hard fork of the Rust Kaspa node introduced KIP-9, KIP-10, and TX payload field activation. A hard fork is a code change that makes the new node incompatible with the old one — both sides can no longer talk to each other, so a separate node build is needed to participate. KIP stands for Kaspa Improvement Proposal, the process the Kaspa project uses to define and adopt protocol-level changes. The TX payload field is an area within a Kaspa transaction that can carry extra data. Together, these additions make TN-11 a meaningful environment for testing features that are not yet live on mainnet. Understanding what a testnet introduces helps you decide whether TN-11 is the right network for whatever you are building or testing on Kaspa.