Polkadot governance has approved and executed referendum 1944, authorizing the creation of dotUSD as a protocol-owned stable-value asset and committing treasury resources to its initial liquidity. The on-chain governance record was marked “Executed” when checked on 12 October 2026.

The decision is material for Polkadot’s decentralized-finance infrastructure, but it does not mean the complete DOT-backed stablecoin system is already operating. The approved proposal separates the rollout into two phases. Phase one uses USDT as backing; the more complex system of DOT-collateralized vaults, oracle pricing, liquidations and direct redemptions is reserved for phase two.

What referendum 1944 approved

The referendum authorizes seven linked actions: create the dotUSD asset, recognize it as Polkadot’s native stablecoin, create a DOT/dotUSD pool on Asset Hub, seed that pool with treasury funds, make dotUSD a “sufficient” asset that can be held without a separate DOT balance, set the initial peg-stability-module parameters and create a coinage instance.

The initial liquidity plan allocates $2.5 million of USDT to mint dotUSD and $2.5 million worth of DOT to the DOT/dotUSD pool. That is a planned treasury-funded pool composition, not evidence of $5 million of organic user demand or trading volume.

Subsquare’s final tally shows 98.5% aye and 1.5% nay, representing about 4.63 million DOT voting aye and roughly 70,810 DOT voting nay. Reported support was approximately 1.87 million DOT. The large percentage margin establishes the vote result; the absolute participation and subsequent usage remain separate questions for the market.

Phase one still depends on USDT

The proposal says the first phase is already built and on-chain. In this stage, users can mint dotUSD one-for-one against USDT, subject to a cap, through a peg-stability mechanism. The corresponding dotUSD can be redeemed against the stablecoin buffer.

This structure avoids the need for an oracle, individual debt vaults or liquidation logic at launch. It gives applications a simpler asset to integrate while the full design is developed. It also creates an important qualification: although dotUSD is intended to be protocol-owned and governed by Polkadot, phase one inherits counterparty and control risks from the USDT that backs the buffer.

The governance proposal describes dotUSD as having no conventional issuer and operating through on-chain logic. That claim describes the protocol design. It should not be read as eliminating the external risks of every collateral asset used by the system.

DOT-backed vaults come later

Phase two would introduce the feature that connects dotUSD more directly to DOT’s economics. Users would lock DOT as over-collateralized backing and mint less dotUSD than the market value of that collateral. If a vault fell below the required collateral ratio, the position could be liquidated.

The proposed model draws on Liquity v2. It calls for an oracle, a stability pool, liquidation mechanics and a redemption path through which dotUSD could be exchanged for DOT. Vault owners would set their own interest rates, with lower-rate positions facing earlier redemption pressure.

None of those phase-two mechanisms should be treated as live merely because referendum 1944 executed. They introduce oracle risk, smart-contract risk, liquidation design questions and the possibility of reflexive stress if falling DOT prices weaken collateral while redemptions or liquidations add pressure to DOT markets.

The referendum also states that its preimage depends on Polkadot system chains being upgraded to version 2.5 under referendum 1942. That dependency makes implementation status—not the governance vote alone—a necessary part of judging rollout progress.

Why the decision matters

A native stable-value unit could reduce friction for Polkadot applications that currently rely on assets issued or governed outside the network. It could also provide a dollar-denominated unit for treasury operations and other parts of Polkadot’s evolving economic model.

For DOT, the immediate effect is limited. Treasury DOT is intended for pool liquidity, but phase one does not establish broad DOT collateral demand. A stronger structural link would emerge only if phase-two vaults launch safely and users choose to lock meaningful amounts of DOT to mint dotUSD.

Liquidity quality also matters. A treasury-seeded pool can make initial swaps possible, but sustainable utility depends on third-party integrations, stable peg behavior, recurring volume and sufficient exit liquidity under stress. Approval does not prove those outcomes.

NetNapz assessment

Facts: referendum 1944 is marked executed; it authorizes dotUSD, a DOT/dotUSD Asset Hub pool and an initial treasury allocation of $2.5 million in USDT plus $2.5 million in DOT. Phase one is a capped USDT-backed design. DOT-collateralized vaults are a later phase.

Inference: the phased approach reduces launch complexity, but it postpones the part of the design most likely to create direct collateral demand for DOT. In the near term, dotUSD should be assessed primarily as a protocol-governed wrapper around a USDT buffer, not as a functioning large-scale DOT-backed credit system.

Constructive case: the case strengthens if dotUSD supply grows alongside real application use, the DOT/dotUSD pool develops resilient two-way liquidity, the peg remains stable, and phase two launches after independent audits with transparent oracle and liquidation parameters. Under that scenario, locked DOT and dollar-denominated network activity could reinforce one another over a multi-quarter horizon.

Risk case: limited integrations, shallow non-treasury liquidity or persistent dependence on USDT would weaken the native-stablecoin thesis. A delayed phase two would postpone the DOT-collateral link. After phase two, oracle failures, liquidation cascades or an unstable peg would become the main technical and market risks.

What to watch: the actual dotUSD asset supply, the PSM cap, Asset Hub pool depth and volume, third-party wallet and application integrations, confirmation that system-chain upgrade dependencies are complete, published audits, and a dated launch plan for DOT-backed vaults.

Sources

• Polkassembly: Referendum 1944 — dotUSD: A Native Stablecoin for Polkadot, archived governance proposal and executed status checked 12 October 2026.
• Subsquare: Polkadot Referendum 1944, executed status, tally and proposal text checked 12 October 2026.
• Subsquare: Polkadot Referendum 1942, system-chain upgrade dependency cited by referendum 1944.

No RSS, imported-feed or News Wire material was used.