Skip to content

Algorithmic Stablecoins: Peg, Redemption and Death-Spiral Risk

A balance-sheet and market-liquidity framework for evaluating rule-based stablecoins, redemption rights, endogenous collateral, dilution and run risk.

Updated

For educational purposes only; not investment advice. Stablecoins can lose their peg, suspend redemption, become illiquid, or impose losses on holders.

Direct answer

“Algorithmic stablecoin” is not a standardized risk class and does not necessarily mean uncollateralized. Rule-based designs include rebasing supply, seigniorage or dual-token conversion, partial external reserves, crypto collateral and hybrids. Evaluate the exact contracts and claims, not the label.

Start with four ledgers: stablecoin liabilities, external reserves, the executable value and dilution capacity of an endogenous loss-absorber token, and protocol equity or other backstops. Then separate contractual or on-chain primary mint and redemption from the secondary-market price. A token trading near $1 does not prove that every holder can redeem at par.

How it works

  1. Pin the chain, stablecoin and absorber contracts, implementation version, reference unit, oracle, administrators, pause roles and any legal issuer or custodian.
  2. Classify the mechanism: external reserve, overcollateralized debt, partial or hybrid backing, rebasing, seigniorage shares, dual-token conversion or another rule set.
  3. Reconcile stablecoin liabilities, eligible external reserves, collateral haircuts, endogenous absorber capacity, protocol equity, bridge supply and in-flight claims without double counting.
  4. Document who can mint or redeem, the delivered asset, oracle and price formula, fees, caps, queues, cooldowns, eligibility, pause conditions and settlement finality.
  5. Test premium and discount arbitrage with executable depth, latency, gas, slippage and absorber liquidity; the quoted conversion is not a riskless fill.
  6. Stress collateral prices, correlated absorber decline, oracle failure, liquidation congestion, bank runs, governance changes, bridge or custodian failure and bad-debt waterfalls.
  7. Publish peg and redemption triggers, reserve and supply monitoring, admin-change alerts, position limits, exit routes and recovery, migration, legal and tax assumptions.

Examples

  • Above peg, an authorized trader converts $10,000 of value into 10,000 stablecoins and sells at $1.03, producing $10,300 and $300 gross arbitrage. If gas and slippage total $40, net is $260, only if mint and sale both execute.
  • Below peg, buying 10,000 stablecoins at $0.97 costs $9,700 and a par redemption appears to return $10,000. But a 4% execution haircut returns $9,600, so result is 9600-9700 = -$100 before gas.
  • Stable liabilities are $100 million; external collateral is $55 million and a backstop is $15 million, so coverage is 70%. A 25% collateral loss leaves $41.25 million+$15 million = $56.25 million, or 56.25% coverage and a $43.75 million shortfall.
  • Absorbing $20 million of redemption by minting the volatile token at $10 requires 2 million tokens. If its price falls to $4 before sale, those tokens are worth $8 million, leaving a $12 million gap; filling that gap at $4 requires 3 million more tokens, illustrating reflexive dilution.

Risks

  • Holders have no enforceable or accessible par-redemption right.
  • Redemption is restricted by eligibility, identity, geography or minimum size.
  • Caps, queues, cooldowns or pauses block contraction when demand falls.
  • The oracle is stale, manipulated or uses the wrong reference market.
  • Primary conversion and secondary executable prices diverge.
  • Endogenous collateral and the loss absorber collapse together.
  • External reserves suffer credit, custody or market-value losses.
  • Reserve assets cannot be liquidated without a fire-sale discount.
  • Liabilities exceed haircut-adjusted assets and create bad debt.
  • Liquidation congestion or penalties amplify collateral losses.
  • Minting the absorber token causes reflexive dilution and a death spiral.
  • Coordinated redemptions exhaust liquidity and trigger a run.
  • Secondary markets become shallow, fragmented or unavailable.
  • Governance or an administrator changes parameters, upgrades or freezes contracts.
  • Smart-contract, decimal or accounting errors corrupt mint, burn or reserve ledgers.
  • Bridges, custodians, issuers or cross-chain messages fail.
  • Blacklists, freezes, sanctions or regulation limit transfer and redemption.
  • MEV, slippage, gas and chain congestion defeat the arbitrage path.
  • Yield depends on subsidies or new inflows rather than external revenue.
  • Fork, migration, recovery, tax or disclosure failures spread losses to connected protocols.

Common misconceptions

  • Algorithmic means uncollateralized. Many systems combine rules with external or crypto collateral.
  • Code guarantees a $1 peg. Code executes rules; it cannot create reserve value or market demand.
  • A discount always creates risk-free arbitrage. Caps, fees, queues, slippage and falling absorber value can reverse the trade.
  • A long historical peg proves solvency. Past balance does not prove run-time redemption capacity.
  • High yield is external economic revenue. It may be emissions, leverage or incentives funded by new users.

Sources

Navigation

Search the wiki...