As a natural next step in the evolution of this forum, we created a kaspanet repo for converging on actual, formally defined specs and conventions:
Each KCC is meant to be a Kaspa Call for a Convention: a document specifying a convention around which independent ecosystem participants and implementations may converge. Topics may include covenant conventions, script ABIs, asset standards, wallet and indexer interoperability, based applications, and other areas where independent implementations benefit from convergence.
Unlike KIPs, KCCs concern ecosystem agreement rather than changes to Kaspa core infrastructure – for instance, the proposed KIP-12 browser-extension wallet API, originally in PR 21 and continued in PR 44, would now fit more naturally as a KCC.
This is just the first step. The repo is meant to provide a home and coordination point for the effort, while leaving room for the process itself to be shaped by people willing to take serious initiative and responsibility.