INDEPENDENT KASPA COVERAGE
Kaspa News
Kaspa logoKAS / USDLoading quote…Price updates every 60 secondsCoinGecko ↗
← News

KAS20 could give Kaspa token markets a common KAS asset

A proposal would put KAS into the same token interface as other KCC-20 assets. The code is still under review. For traders, the central question is whether wallets and markets will recognize one backed, redeemable version of KAS.

Editorial illustration of teal light flowing from one central reserve into connected market channels
Illustration by Kaspa News.

A new Kas-Smiths proposal asks a practical question about Kaspa trading: when a decentralized exchange handles KCC-20 tokens, what should it use as the KAS side of a pair? Native KAS already exists as value in Kaspa's transaction outputs. But an app designed around the KCC-20 token interface cannot treat native KAS exactly like every other token without adding separate logic.

The proposed answer is KAS20, a KCC-20 representation backed by KAS. A general-purpose pool could then handle a KAS20/token pair using the same interface it uses for two other KCC-20 assets. The author presents this as a way to simplify application design, not as a claim that a DEX cannot support native KAS directly.

What would make one KAS20 worth one KAS?

Under the proposed design, each KAS20 base unit is backed by one sompi held in its token output. With eight decimals, 100 million units represent one KAS20 backed by one KAS. Anyone could mint by locking the matching amount of KAS, then transfer the token through the KCC-20 interface. Burning would release the backing KAS, less transaction fees. That is the proposal's mechanism; a ticker or name alone would prove none of it.

The companion reference-code pull request remains open. It includes an offline demo that mints, transfers and burns KAS20 in a test flow. The author reports that its reference and KAS20 tests pass. An offline demo is useful engineering evidence, but it is not a live market, a security audit or a guarantee that a production wallet will support this token.

The market problem is bigger than the code

The proposal's author notes that several teams could deploy different KAS-backed KCC-20 tokens. If one DEX lists version A, another lists version B and a wallet recognizes only version C, liquidity could split across assets that all claim to represent KAS. A common implementation and deployment could make quoting, routing and wallet support simpler. Whether the ecosystem actually converges is a coordination question that code alone cannot settle.

For a trader, this is an inference from the proposal, not a prediction about volume. Shared liquidity may improve the chance of usable depth and clearer prices, while fragmented pools can make execution more confusing. Neither outcome is guaranteed. A pool's real depth, fees and slippage will have to be measured once any market exists.

What to check before treating a listing as KAS-backed

First identify the exact deployed covenant or token identifier from an official source, rather than trusting a symbol. Then check the published implementation, how its backing can be verified, whether redemption is available to ordinary holders and what fees or restrictions apply. Look for independent review and a wallet that correctly displays the token and redemption flow. Finally, check which exchanges and pools actually use that same identifier, and whether their order books or pools have enough liquidity for the size of a trade.

Those are questions for future deployments. We have not verified a live KAS20 token, a mainnet KAS20 market or a commitment from the launchers in our directory to support this implementation. A project using the name KAS20 should not be assumed to be the version described in the open proposal.

What comes next

The KCC-20 convention is marked Final. The standards repository explains that this status marks ecosystem convergence on a convention. It does not change Kaspa consensus or automatically deliver wallet, exchange or application support. The KAS20 proposal itself asks for feedback, and its example code is still an open pull request.

We will watch for a reviewed implementation, a declared deployment identifier, evidence of backing and redemption, and statements from wallets and trading venues about which KAS representation they plan to support. Until then, KAS20 is a potentially important market design, not a trading instruction.

Publisher disclosure

Kaspa News covers an ecosystem in which its publisher has created projects and holds crypto assets. This article is reporting on a technical proposal. It is not an endorsement of a token or a recommendation to trade.

Primary sources