𝑹𝑬𝑪𝑶𝑵

Kaspa & PoW Architecture | Institutional grade research
on protocol development, on chain data & ecosystem
Weekly deep dives. No hype. Systems over Speculation.

[𝑹𝑬𝑪𝑶𝑵 @ReconProtocol]

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. 🧵

[𝑹𝑬𝑪𝑶𝑵 @ReconProtocol]

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: https://t.co/iQMLMGz28f, 24.10.2026.

#KAS #NFA

[𝑹𝑬𝑪𝑶𝑵 @ReconProtocol]

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

[𝑹𝑬𝑪𝑶𝑵 @ReconProtocol]

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.

[𝑹𝑬𝑪𝑶𝑵 @ReconProtocol]

@michaelsuttonil Curious which piece you see as the actual protocollevel blocker, since covenants can't natively pull in a price feed. Is a ZK verified oracle commitment the planned route for liquidation triggers, or something else entirely?

[𝑹𝑬𝑪𝑶𝑵 @ReconProtocol]

@BankQuote The actual x402 on Kaspa build that exists right now is testnet-10 only, the project explicitly says it's not a mainnet readiness claim. It leans on KIP-20 to keep payment channel identity stable across top ups and partial claims. Real groundwork, just still early groundwork.

[𝑹𝑬𝑪𝑶𝑵 @ReconProtocol]

Worth flagging, Kasplex has now spelled out the exact rule behind this gap, certain old transactions simply can't have their fees calculated because the historical data needed for that got cut off at a specific point, so those got silently skipped rather than rejected. A fix already exists going forward so this won't happen again. Also, NACHO's move to the new KCC-20 token standard works by re issuing tokens people submit, not by snapshotting balances, so this old gap matters a lot less than it sounds.

[𝑹𝑬𝑪𝑶𝑵 @ReconProtocol]

@KaspaHub @asaefstroem Where's this sourced from, haven't seen a direct confirmation from @asaefstroem's own account yet on this, or did I miss it?

[𝑹𝑬𝑪𝑶𝑵 @ReconProtocol]

@KaspaKing1 Worth being precise, there's no actual wrapping vault here. Each UTXO holds the real KAS directly alongside the KCC-20 state, per Michael Sutton's own explanation yesterday. Also still just a proposal under discussion right now, not shipped yet.

[𝑹𝑬𝑪𝑶𝑵 @ReconProtocol]

9/9
Question for operators running rusty kaspa in production, has the 2.1.0 upgrade gone through on your side yet, and did the chunked IBD change anything measurable in your sync times?

[𝑹𝑬𝑪𝑶𝑵 @ReconProtocol]

1/9
rusty-kaspa v2.1.0 shipped October 4, 2026. It is not a feature release wrapped in marketing language. It is a security and maintenance release, and the detail work in it is worth more attention than it got.
kaspa:native

[𝑹𝑬𝑪𝑶𝑵 @ReconProtocol]

8/9
The release notes explicitly recommend node, mining, and infrastructure operators upgrade. That is not boilerplate. A path traversal patch and a key comparison fix are the kind of items you do not sit on.