Stablecoin Peg Stability Module
Abbreviation: PSM
Pronunciation: STAY-buhl-koyn PEG stuh-BIL-uh-tee MOD-yool
Also known as: Peg Stability Module, PSM
Definition
Stablecoin Peg Stability Module is a protocol facility that supports a stablecoin’s target price by allowing specified assets to be exchanged, minted, redeemed, borrowed, or otherwise routed under predefined pricing and fee rules. A PSM is one possible peg mechanism, not a guarantee of stability. Its design differs from open-market trading, collateral liquidation, issuer redemption, or discretionary treasury intervention. Operationally, operators monitor eligible assets, swap direction, price, fees, debt or capacity ceilings, reserves, oracle assumptions, pause controls, governance changes, and concentration in counterparties or collateral. Bad collateral, depleted capacity, governance delay, oracle error, smart-contract failure, regulatory freezing, and one-sided flows can disable the module or transmit external stablecoin risk.
Overview
Stablecoin Peg Stability Module is a protocol facility that supports a stablecoin’s target price by allowing specified assets to be exchanged, minted, redeemed, borrowed, or otherwise routed under predefined pricing and fee rules. Stable-value systems must be evaluated across issuance, reserves or collateral, redemption, liquidity, governance, legal claims, and operational dependencies.
A PSM is one possible peg mechanism, not a guarantee of stability. Its design differs from open-market trading, collateral liquidation, issuer redemption, or discretionary treasury intervention. It should be read alongside Retail Stablecoin, Redemption Delay, Reservoir Stablecoin (rUSD). These concepts describe adjacent but different layers of the asset, so substituting one for another can hide the governing network, holder claim, authority, supply measure, or operational action.
Operationally, operators monitor eligible assets, swap direction, price, fees, debt or capacity ceilings, reserves, oracle assumptions, pause controls, governance changes, and concentration in counterparties or collateral. A production system should preserve the network, contract or asset identifier, units and precision, governing rule version, responsible authority, effective timestamp, and transaction or external record used to support the state shown to a user. Changes should be observable, reconciled, and tested across deposits, transfers, withdrawals, upgrades, and exceptional cases.
Bad collateral, depleted capacity, governance delay, oracle error, smart-contract failure, regulatory freezing, and one-sided flows can disable the module or transmit external stablecoin risk. Teams should test failed transactions, unavailable indexers or external services, compromised keys, stale metadata or prices, contract and protocol upgrades, chain reorganizations, role changes, and inconsistent records between blockchain, market, custody, legal, and accounting systems.
For due diligence, identify the legal issuer or protocol, the holder’s claim, direct redemption eligibility, price and fees, reserve or collateral evidence, administrator powers, and stress procedures. Monitoring should cover privileged-role events, supply or ownership changes, contract migrations, parameter updates, redemption or transfer exceptions, and evidence that the represented rights remain enforceable. This makes Stablecoin Peg Stability Module an auditable operational concept rather than a label accepted only from a wallet, marketplace, or issuer interface.
Key Takeaway
Stablecoin Peg Stability Module must be verified through its authoritative network or contract, current control and supply rules, and the legal or operational rights actually attached to it.
Sources
- MIP29: Peg Stability Module — Maker Improvement Proposals (2026-08-02)
- DSS Lite Peg Stability Module — MakerDAO (2026-08-02)
- High-Level Recommendations for Global Stablecoin Arrangements — Financial Stability Board (2026-08-02)