Pinned Tweet
1/10
Kaspa is joining the global payment standard for the internet.
x402 founded by Coinbase and Cloudflare,
now a Linux Foundation project is becoming the default way AI agents pay for APIs and data.
This week, a kaspa:native binding is ready for upstream submission.
Here's why it matters. 馃У
馃 Made with AI
1/10
Kaspa's token standard is now final.
KCC-1, KCC-2 and KCC-20 were finalized on October 21. Michael Sutton co authored all three. Ori Newman co authored KCC-1 and KCC-20. Their KIP-20 covenant IDs and KIP-17 opcodes went live in Toccata.
Five authority schemes. One shared ABI. One token covenant. Here is what it means 馃У
kaspa:native
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
Sources, KCC specifications and status index at kccs.dev, silverscript v1.0.0 and rusty-kaspa v2.0.1 release notes on GitHub.
1/
Kaspa's top 10 addresses hold 25.8% of circulating supply.
The number alone sounds like a centralization headline.
The composition behind it tells a different story.
kaspa:native
9/
That combination matters for how a sell off would actually propagate. A dump from the top 14 is a single coordinated event risk. A dump from 2,968 independent Shark tier wallets is not coordinated by definition, it is a market wide behavior shift.
Two different risk profiles, same supply share.
10/
Distribution Watch runs monthly. Same methodology, same source, tracked over time.
Open question for this one: what would move Entity X from "unlabeled" to identified, and would that change how the market prices this asset?
Data: kaspa.stream, 24.10.2026.
#KAS #NFA
