Quiet but big: Kaspa's standards process just proved it works. 🏁 KCC-0 β€” the document that defines HOW Kaspa conventions get finalised β€” reached Final on Sept 21. The first KCC ever to cross the line. πŸ“£ And now KCC-20, THE covenant token standard, has an open PR proposing Last Call β€” the final review stage before Final. Also in the pipeline: a wallet API standard (KCC-12), covenant metadata (KCC-23), and a brand-new domain β€” reputation, bonds and identity as covenants. No foundation decree. No backroom. Every stage change is a public pull request anyone can read. That's how you grow a standard.

Sep 24, 2026 Β· 6:48 PM UTC

3
19
78
1,695
Follow it yourself: All 4 proposals, tracked daily with state badges β†’ kasstacker.org/status The standards repo β†’ github.com/kaspanet/kccs Where they're debated β†’ kas-smiths.org Core R&D Telegram (public) β†’ t.me/kasparnd The badge on our status page flips the day KCC-20 merges. Watch it.
4
138
Sort replies: Relevant Recent Liked
πŸ”₯
1
21
Replying to @GoonBoyCrypto
A standards process that runs entirely through public pull requests changes who can participate. Not just core devs anyone can read the state change, trace the reasoning, propose Last Call. KCC-20 reaching review stage this way matters more than the standard itself.
1
58