On the rest is free half of that proof, does a wallet need the complete name set to check absence, or is there a compact commitment it can verify against L1 state instead?

Consensus guarantees a .k name is unique, but a wallet still has to find it, and as of August no node RPC listed UTXOs by covenant ID. Is the dotK indexer the only resolution path for wallets like Kastle and KasWare, or can they verify a name directly against L1 state?

Three registries in one wallet, and dotK is already in a second one, Kastle added it earlier this week. Since .k names live as covenants, Kaspa's own consensus guarantees each name is unique, no registrar needed.

The good news for any wallet team is that KCC-20 needs no node upgrade, only work on the wallet side. An open reference implementation with conformance tests is already public, and Kasla has added KCC-20 sending and receiving. Thanks for passing it on to the team.

The new chat per task tip is the one most people skip, and it quietly adds up. Curious where you draw the line between Sonnet and Opus when it comes to content work.

The plan behind it is more concrete than the headline suggests. A first testnet version is set for May 2027, with the production release following in September. The 5 million KAS goes into development, research and an independent audit, not into the collateral itself.

Kaspa 2.1 changes how a node syncs, large data like pruning proofs now arrives in 20 MiB chunks. The release also closed several bugs that could crash or overload a node, none of them touching consensus.

Writing those rules got much simpler with Silverscript 1.0 in September. A token mechanism that once took thousands of lines of raw opcode code now fits in about 60 readable lines, and the network still enforces every one of them.

Two dozen transactions a day created covenant outputs in July. By mid August it was still around 750 a day, roughly thirty times that, according to Kaspalytics. Those are the Kaspians who keep building, showing up in the code.

The best part of dotK is who guarantees a name is unique. No registrar decides it, Kaspa's own consensus enforces it through .k covenants. Great to see that now living inside Kastle.

What makes KAS20 different from WETH is that there's no shared vault at all. Each UTXO carries the real KAS and its KAS20 balance together, so no single contract ends up holding everyone's coins, as Michael Sutton explained last week.

Sources, KCC specifications and status index at kccs.dev, silverscript v1.0.0 and rusty-kaspa v2.0.1 release notes on GitHub.

10/10 Capability shipped in June. Conventions shipped on October 21. Adoption is the open question. What lands first, wallet support for KCC-20 or the first covenant DEX pool? Data as of October 24, 2026. #NFA

9/10 What Final means under KCC-0. Machine readable test vectors, at least one public implementation that passes them, finalized dependencies and a security section. It does not change consensus and it does not force anyone to adopt it. According to developer discussion on Discord, implementation is wallet side and needs no new node release.

8/10 The tooling already exists. A reference implementation ships with generated SilverScript contracts and Rust conformance tests. SilverScript v1.0.0, released September 10, compiles typed contracts directly to native Kaspa Script and cut the token mechanism from thousands of lines of opcode building to about 60 lines.

7/10 The standard states its own cost. Borrowed Receive replaces the recipient's output, so its outpoint reference changes. Unconfirmed transactions that spend the old reference become invalid. Wallets have to detect the replacement before they spend. This is a design trade off written into the spec, not a footnote.

6/10 Four borrow schemes decide who may add tokens to an output. Disabled, amount threshold, Schnorr signature, or hash chain. The recipient chooses how open the output is to incoming transfers.

5/10 The mechanism worth understanding is Borrowed Receive. In a UTXO model, a transfer normally needs a new output for the recipient, and under Kaspa's storage mass rules that output has to carry KAS. With Borrowed Receive, the sender uses the recipient's existing compatible token output as the destination. It is recreated with more tokens, so no new KAS funded output is needed.

4/10 KCC-20 is the fungible token covenant. Each token output carries a state with amount, owner, owner scheme, borrow scheme, borrow guard and an extension commitment. The token lives in the UTXO itself. No global contract storage holds the balances.