One of the most common questions in the Kaspa community is: when will Kaspa have a native stablecoin? A native stablecoin: one minted and redeemed on Kaspa itself, backed by KAS collateral: is the holy grail for Kaspa DeFi. It would unlock deep liquidity, enable lending markets with stable-denominated borrowing, and attract a new wave of users and capital to the ecosystem.
As of June 2026, Kaspa does not yet have a native stablecoin. However, the pieces are falling into place, and there are three distinct paths to getting one. This guide explains what a stablecoin needs, the three paths available, the current state of play, and a realistic timeline.
A decentralized, over-collateralized stablecoin (like MakerDAO's DAI) requires several components to function securely:
Approach: Fork an existing Ethereum stablecoin protocol (DAI or FRAX) and deploy it as an ERC-20 contract on Kasplex L2 (zkEVM). Since Kasplex is EVM-compatible, existing Solidity code for CDPs, oracles, and liquidation engines can be ported with minimal changes.
Pros: Fastest to market: a working DAI fork could be deployed on Kasplex testnet within weeks. Leverages existing, battle-tested code. Full composability with other Kasplex dApps (Zealous Swap, Kaskad Lending).
Cons: Runs on L2, not L1: inherits bridge risk and sequencer trust assumptions. Still needs an oracle for KAS/USD on Kasplex (which doesn't yet exist in production).
Approach: Use Toccata's SilverScript covenants to create a trust-minimized vault that locks KAS and issues a stablecoin token via native assets. The covenant enforces the collateral ratio and liquidation rules without a full smart contract runtime.
Pros: Runs on L1 directly: no bridge or sequencer trust. Inherits Kaspa's full PoW security. No EVM dependency.
Cons: SilverScript is not Turing-complete: complex CDP logic (variable interest rates, multi-collateral support, sophisticated liquidation auctions) may be infeasible. No shared state between covenant instances, making composability across vaults difficult. Oracles would need to be embedded as covenant parameters, which is cumbersome.
Verdict: A simple, single-collateral vault may be possible as an experiment in 2026 H2, but a full-featured stablecoin is unlikely via this path alone.
Approach: Build the entire stablecoin system: CDP, oracle integration, liquidation engine, and governance: as a Based ZK Rollup on vProgs (Tier 3). All logic runs off-chain, with ZK proofs submitted to L1. The rollup maintains its own state tree for CDP positions, enabling full composability.
Pros: Fully featured: supports multi-collateral CDPs, variable interest rates, sophisticated liquidation auctions, and governance. Composable with other vProg-based DeFi protocols. Settles on L1 via ZK proofs: inherits Kaspa's security. No bridge risk (native L1 settlement).
Cons: Requires vProgs Phase 2 (full composable vProgs), which is targeted for 2027. Longer wait. Requires proving infrastructure and oracle integration within the ZK rollup.
Verdict: The endgame: a fully native, feature-complete stablecoin that leverages Kaspa's unique architecture. But requires patience.
| Feature | Kasplex L2 ERC-20 | L1 Covenant Vault | vProgs Native Stablecoin |
|---|---|---|---|
| Availability | Now (testnet) / Late 2026 (mainnet) | 2026 H2 (experimental) | 2027–2028 |
| Execution Layer | Kasplex L2 (zkEVM) | Kaspa L1 (covenants) | vProgs (L1 via ZK proofs) |
| Trust Model | Bridge + sequencer | L1 PoW only | L1 PoW + ZK proofs |
| Turing Completeness | Full (EVM) | Limited (SilverScript) | Full (Noir/Rust/Cairo) |
| Composability | Full EVM composability | Limited (no shared state) | Full (vProg rollup composability) |
| Oracle Integration | Needs Kasplex oracle (not yet built) | Embedded covenant parameters | Native vProg oracle module |
| Liquidation Engine | Smart contract (battle-tested code) | Covenant-enforced (limited complexity) | Full programmable engine |
| Complexity | Low (fork existing code) | Medium (custom covenant design) | High (vProg development) |
Here's exactly where things stand as of mid-2026:
To summarize the critical gaps that need to be filled before a native Kaspa stablecoin can launch:
| Phase | What Happens | Timeline |
|---|---|---|
| Kasplex L2 Stablecoin Fork | A team forks DAI or FRAX and deploys on Kasplex L2. Requires oracle infrastructure and mainnet launch of Kasplex. Most likely first path to a KAS-backed stablecoin. | Now – Late 2026 |
| L1 Covenant Vault (Experimental) | A simple single-collateral vault using SilverScript covenants. Limited functionality but runs entirely on L1. Useful as a proof-of-concept and for small-scale experimentation. | 2026 H2 (experimental) |
| vProgs Phase 1 — Standalone Apps | Based ZK Apps become available. Individual CDP-like applications possible, but no shared state across vaults. | 2026 H2 |
| vProgs Phase 2 — Full Composability | Based ZK Rollups with shared state. A full-featured vProg stablecoin (CDP + oracle + liquidation + governance) becomes technically feasible. | 2027 |
| Mature vProg Stablecoin | Multi-collateral support, sophisticated liquidation auctions, DAO governance, integration with multiple Kaspa dApps. The end-state vision. | 2027–2028 |
While a native stablecoin is still on the horizon, it's worth highlighting Kaskad Lending: the first lending protocol on Kaspa, launched on Kasplex L2 with $2M TVL as of June 11, 2026. Kaskad may not be a stablecoin itself, but it provides the essential infrastructure that a stablecoin needs:
Kaskad's rapid growth ($2M TVL in its first weeks) is the clearest signal yet that the Kaspa community is ready for DeFi: and that a native stablecoin would find immediate product-market fit.