What problem does KIP-20 solve for Kaspa covenant applications?

KIP-20 removes the heavy overhead that Kaspa covenant applications previously needed just to prove their own identity across transactions. Before KIP-20, covenants built on KIP-17 (Kaspa's transaction-introspection proposal) had to carry parent and grandparent transaction data as "witness" baggage every time a coin was spent — extra information bundled into the transaction solely to prove lineage. This made covenant contracts larger and forced them to depend on the exact internal way Kaspa encodes and hashes transactions, a fragile dependency. KIP-20 introduces a native, consensus-enforced lineage mechanism so developers can build stateful Kaspa applications without those recursive proof workarounds.