Proposal “dusd-dash-native-stablecoin“ (Active)Back

Title:dUSD - Native, Over-Collateralized Stablecoin on Dash Platform
Owner:DavidLen
Monthly amount: 608 DASH (25760 USD)
Completed payments: no payments occurred yet (2 month remaining)
Payment start/end: 2026-05-17 / 2026-07-25 (added on 2026-05-06)
Final voting deadline: in 2 months
Votes: 55 Yes / 170 No / 27 Abstain
Will be funded: No. This proposal needs additional 427 Yes votes to become funded.
Manually vote on this proposal (DashCore - Tools - Debugconsole):
gobject vote-many 3f6ce7a57e2ffa2528a38309889cf5ac8db85155edb0e2280ba048961aa3edba funding yes

Please login or create a new DashCentral account for comfortable one button voting!

Proposal description

Development funding (testnet  Total ask: 1825 DASH (~$83K USD at original submission rate) — 608 DASH per monthly cycle × 3 cycles, milestone-gated

TLDR



dUSD is the first DASH-backed over-collateralized stablecoin on Dash Platform, letting users save and spend in a stable unit without leaving the ecosystem.

Users currently off-ramp to USDT for stability, taking their balances and the merchant network effects with them. dUSD locks DASH in vaults to mint a stable unit, creating sustained demand for DASH while keeping value inside the ecosystem.

This proposal funds: A working CDP core (mint/redeem) on Dash Evolution testnet.

Model: Based on Liquity's LUSD.

Trustless: No banks, no KYC, and no off-chain reserves.

The Problem: Dash Capital Leakage



Dash has spent years building the hardest part of the crypto economy: a working real-world payment network. With deep merchant adoption across the global south, it operates one of the most established and decentralized payment networks among top-tier cryptocurrencies. But the network is suffering from a structural capital leakage.

The Paradox of Choice



In volatile economies like Nigeria and Venezuela, local currencies are failing faster than DASH can stabilize. Venezuela's annual inflation hit 650% in March 2026. The Nigerian naira fell from roughly ₦460 to ₦1,500 per US dollar within three years, a loss of more than 60% with headline inflation still around 20% in late 2025.

Users in these regions don't just want speed; they need a unit of account that holds value overnight. Currently, they are forced to choose between the utility of Dash and the stability of the US dollar. Stability is winning, leading to a predictable Leakage Path:

  • Receive: a user receives DASH (fast, cheap, censorship-resistant).
  • Park: they immediately bridge or off-ramp to a stable coin like USDT on TRON or Ethereum to park value.
  • Loss: Dash captures the transaction but loses the balance sheet. The chain that holds the savings wins the user.

The Macro Shift: Stablecoins as a Global Layer



Stablecoins are no longer a niche crypto tool; they are a global financial layer that users are "voting" for with their balances. The scale is staggering:

  • Market dominance: Total capitalization crossed $312 billion in October 2025, climbing to $320 billion by early 2026.
  • Massive throughput: In 2025, stablecoins processed $33 trillion in transactions, a 72% year-over-year increase with monthly peaks approaching the throughput of the Visa network.
  • The Global South factor: More than 80% of these flows occur outside the U.S., specifically in markets plagued by currency instability and limited dollar access. These are the exact regions where Dash spent years building its merchant base.

The Irony of Defection



The problem isn't the spending rail. Between USDT-on-TRON QR networks and stablecoin-linked debit cards (which saw a 673% YoY increase in volume), the infrastructure for stable payments is already live in Dash's core markets.

Dash users are not defecting because Dash failed to provide fast, cheap, or censorship-resistant payments. They are defecting between transactions to park their value in something stable. However, in seeking price stability, they are unwittingly reintroducing the exact failure modes Dash was built to avoid:

  • Issuer freeze risk: Two companies (USDT and USDC) control 93% of the market.
  • Legacy dependency: These assets are bound by U.S. banking regimes, KYC gates, and opaque reserves.

The bottom line: Dash has the better tech, but the market is currently choosing the stability of centralized issuers over the sovereignty of decentralized assets. The challenge isn't the payment; it's the peg.

Why This Design: The Over-Collateralized Model Is Proven



The Liquity model which dUSD adapts is the only major decentralized stablecoin to retain its peg without centralized collateral through the Terra collapse, the FTX failure, and the March 2023 USDC banking crisis. It has run on Ethereum mainnet since April 2021 with no loss of user funds.

NPH on Beam and MUSD on Mezo (a Bitcoin L2) apply similar over-collateralized mechanics in different chain contexts; we have studied both and concluded Liquity V1's specific design single collateral, immutable contracts, Stability Pool as primary liquidator maps most cleanly onto Dash Evolution's architecture.

The Stability Paradox. The risk of centralization is based in history. During March 2023 USDC depeg, centralized "stable" coins (USDC, FRAX, DAI) took over 35 hours on average to recover. Meanwhile, the decentralized LUSD recovered in under 15 hours, seeing its supply grow by 50% that quarter as users sought a truly decentralized refuge.

It is the most stress-tested decentralized stablecoin design in production, rated above the centralized alternatives Dash users are currently defecting to. dUSD adapts it for the one collateral type Dash holders actually have: DASH itself.

By giving Dash users a native stable unit, capital stays on-chain. Spending happens on Dash's existing merchant network with 1–2 second InstantSend confirmation instead of a competitor's rails.

dUSD closes the loop.

Why Now: The Technical Window



For most of Dash's history, a CDP-style stablecoin couldn't be built on Dash; the base chain is optimized for fast payments, not deterministic programmable logic. That changed in 2026.

Q1 2026 brought the Smart Contracts Virtual Machine (SCVM) and IBC protocol to Dash Platform. The architecture is well-suited to a Liquity-style protocol:

  • Tenderdash consensus settles liquidations in-block (no MEV games).
  • The credit-pool model cleanly separates collateral from operating capital.
  • The existing Evonode network (1,000 DASH per node) provides inherited security without bootstrapping a new validator set.

Solution



dUSD is a CDP-style stablecoin issued against locked DASH. Users deposit DASH into a vault, mint dUSD up to a maximum loan-to-value ratio, and can redeem or close the position at any time.

How the peg holds



  • Hard floor — redemption. Anyone holding 1 dUSD can redeem it for $1 worth of DASH at any time, drawing first from the lowest-collateralized vaults. Below-peg trading becomes risk-free arbitrage.
  • Soft ceiling — minting. When dUSD trades above $1, anyone with DASH can mint and sell for profit. The 110% minimum collateral ratio ensures each $1 of dUSD is backed by at least $1.10 of DASH at mint.
  • Stability Pool — liquidation absorption. dUSD holders deposit into a pool that automatically absorbs the debt of any vault falling below 110%, at a discount. Real-time liquidation, no auctions, no keepers.
  • Recovery Mode — circuit breaker. If system-wide collateralization falls below 150%, the protocol tightens liquidation thresholds to restore solvency.

Oracle commitment



A stablecoin is only as honest as its price feed. The protocol uses a Dash-native oracle quorum operated by Evonodes as the primary price source, with Pyth as a deterministic fallback for sanity-checking. This combination keeps trust within the network that already secures Dash, while providing an independent external check against quorum failure or manipulation. Multisig-controlled feed parameters govern fallback thresholds and divergence handling. Full quorum design and fallback behavior will be published before implementation begins in a follow-on cycle.

What is deliberately absent



No multi-collateral, no shared pools. dUSD is backed exclusively by DASH. If future variants are launched (dGold, dGBP, etc.), each is a separate, isolated protocol with its own Stability Pool never a shared pool spanning multiple stablecoins.

Scope and Deliverables (Phase 1)



Specification, threat model, and architecture are being delivered by the team at no cost to MNOs. This proposal funds implementation only.

CycleBuild PhaseDeliverableAsk (DASH)


1Vault primitivesVault data model and storage, collateral deposit, mint with LTV check, fee accrual608
2Position lifecycleRedeem mechanics, repayment, position close, collateral and debt adjustment608
3Testnet integrationTestnet deployment, oracle stub integration, end-to-end test suite, public demo608
Total1,825

Phase 1 success criteria: a user can deposit DASH into a vault on Dash Platform testnet, mint dUSD up to the maximum LTV, repay debt, and close the position. Full mint/redeem lifecycle working end-to-end against the testnet oracle stub.

The 608 DASH per cycle (~$28K USD at submission) covers the development team — two full-time engineers and two part-time contributors — working for three months on implementation.

All code MIT-licensed. Public repo with weekly progress reports on Dash Forum and DashCentral. Each monthly tranche is paid against deliverables already shipped or specified for the following 30 days. MNOs may de-fund any cycle if milestones slip. Subsequent development phases will be proposed as discrete cycles contingent on Phase 1 delivery.

Team



Our team brings engineering experience across Polkadot security infrastructure, Plasma EVM rollups at Tokamak Network, Rust-based vault systems on Solana, and government tooling contributions for Aave, ENS, and Zcash.

Rhovian — Rust/SCVM development and vault logic GitHub
  • Contributor to Boring Vault SVM (collateral and yield management)
  • Rust + iOS (Swift) dual stack


Kos — Liquidation engine, state transition logic, testnet hardening StackOverflow
  • Rust Expert | GPU Engineer | Distributed Systems Engineer
  • Rust blockchain protocol-layer engineering
  • State transitions, consensus interaction, edge-case handling


Lesinwa David — Project Management and system architecture LinkedIn
  • Currently building The Shield, a security layer for Polkadot
  • Government tooling contributions: Aave, ENS, Zcash
  • Systems architecture lead


Carl Park — Lead engineer, smart contract implementation & Liquity-model adaptation GitHub
  • Core Plasma EVM infrastructure at Tokamak Network
  • Plasma EVM contracts, ZK-based DEX
  • Solidity, Go, ZK-proofs


Value to Dash



  • Sustained DASH demand. Every dUSD minted locks DASH in a vault non-speculative demand separate from masternode collateral.
  • Closes the single biggest UX gap in Dash adoption (volatility) without surrendering privacy or decentralization.
  • Aligns with the Evolution roadmap the network has already funded. This proposal builds on, rather than duplicates, prior MNO investment.
  • Bounded downside. Funding is milestone-gated and paid in monthly tranches; if work slips, MNOs cap their exposure to a single cycle.
  • Defensible in the face of the July 2027 EU AML regulation. With the EU AML Regulation banning certain coins effective July 1, 2027, a non-custodial, issuer-less stablecoin gives Dash a defensible product no centralized issuer can replicate.

Prior discussions: https://www.dash.org/forum/threads/pre-proposal-over-collateralized-privacy-stablecoin-for-unstable-economies.69132/

Show full description ...

Discussion: Should we fund this proposal?

Submit comment
 
0 points,9 days ago
The proposal does not outline a clear plan for bootstrapping the initial liquidity of the Stability Pool. Without a sufficient amount of dUSD in the pool from day one, the liquidation mechanism may not function properly - especially during the early stage, when the risk of destabilization is at its highest.

How does the team plan to bootstrap the Stability Pool at launch? Will this be achieved through incentives/rewards, partnerships with market makers, the team’s own liquidity, or some other mechanism? Also, what is the target minimum pool size required before mainnet launch?
Reply
2 points,9 days ago
Hi ravenor,
Thank you for the sharp feedback. To answer this properly, it's important to distinguish between the Phase 1 Testnet build and the Mainnet economic launch.

1. The Redistribution. The Stability Pool (SP) is the primary liquidator, but it isn't the only one. Following the Liquity model, dUSD includes a pro-rata redistribution mechanism. If the SP is ever insufficient, debt and collateral are redistributed across all active vaults. This is the "fail-safe" that kept Liquity solvent during its volatile early weeks when the SP was still filling. The system doesn't "break" without a pool; it just shifts the liquidation burden to the borrowers until the pool recovers.

2. The Bootstrap Strategy. We agree that a naked launch is a non-starter. Our working direction for the Mainnet cycle includes:
Fee Routing: Diverting a portion of borrow/redemption fees to SP stakers (similar to Mezo on a Bitcoin L2).
System-Owned Liquidity: Proposing a Genesis Seed from the treasury to act as a permanent floor **(similar to the Nephrite/BeamX model).**

Guardrail Phase: Unlike Liquity, total dUSD supply is capped based on actual SP depth. Caps lift only after the SP-to-supply ratio holds above a published threshold for a sustained period.
Market maker partnerships: Not pursued at launch, the Genesis Seed plus Guardrail Phase achieves the same backstop without third-party dependencies.

3. Target SP Minimum. 40% of total dUSD outstanding at mainnet enabling, with an automatic mint pause if SP depth falls below 25%. This is more conservative than Liquity's 25-35% empirical equilibrium, justified by DASH's higher volatility profile relative to ETH. During the bootstrap phase, maximum individual vault size will be capped to mathematically bound the worst-case liquidation event.
Reply