five things from this week in Kaspa dev. i have numbered them to appear organized. 1 / KCC standards KCC1, KCC2 and KCC20 are now Final. devs have shared conventions for how covenants, permissions and fungible tokens work together, ready for wallets and apps to adopt. https://x.com/kccforum/status/2112922357979603258 2 / wallet public keys @OriNewman proposed a wallet convention that keeps public keys hidden until funds are spent, reducing their exposure to future quantum attackers. originally KIP22, it’s now under review as a KCC. spending still reveals the key. https://github.com/kaspanet/kccs/pull/37 3 / Kaspa Privacy Initiative @WellerOlaf shared a private-payment experiment on testnet, followed by a recovery test. wallets were restored and the full test balance withdrawn with the original app controller disabled. the rest of the test infrastructure stayed available. still experimental. https://github.com/olafweller/kaspa-privacy-initiative/pull/61 4 / Kastle @KastleWallet added support for dotK names. users can view, register and transfer their .k names inside the wallet. the mobile update is rolling out, with name support also available in the extension. https://x.com/KastleWallet/status/2113537295433490509 5 / KaspaDollar @asaefstroem is leading a new initiative to build an overcollateralized stablecoin on Kaspa, backing each dollar of tokens with more than a dollar of collateral. development, research and an independent audit are still ahead. https://x.com/KaspaDollar/status/2113601328975098237(Historical earnings: For 2026Q2 (period ended 2026-06-30), reported basic EPS of 0.42 and diluted EPS of 0.39, net income of USD 0.103 billion, revenue from contracts with customers of USD 75.207 million, and total revenues of USD 1.395 billion. Consensus expectations: Consensus for 2026Q3 expects EPS of 0.4 and revenue of USD 0.797 billion.)