Kaspa ExplainedRead the proposal
What rule is proposed or specified?
Specifications
Protocol proposals and application conventions
A proposal, implementation, activation, and adoption are separate events. Use the evidence sequence below to place each protocol change or application convention.
Check the software
Which implementation enforces that rule?
Check activation
Is the rule active on the network?
A proposal, software release, and network activation are separate evidence.
Toccata’s active KIPs.
KIP-16 · Proof verification
Supported proof-verification operations.
KIP-17 · Covenants
Transaction introspection and spending constraints.
KIP-20 · Covenant identifiers
Persistent identity for related covenant outputs.
KIP-21 · Sequencing commitments
Commitments that support later verification of ordered activity.
Application conventions and their status
In the September 6 check, KCC-0000 is Last Call. KCC-0001, KCC-0002, and KCC-0020 are Draft. A document’s status does not establish implementation or adoption.
KCC-0020 describes token accounting across covenant outputs. Its open design questions must not be presented as a ratified token standard.
DAGKnight remains a research direction.
KIP-2 is Proposed. Research development is visible, including a September 4 branch commit. That is not a mainnet activation. The checked mainnet release still uses GHOSTDAG.