Algorithmic Stablecoins
Understand algorithmic stablecoins, supply-adjustment mechanisms, reflexivity, partial backing and why price-stability rules can fail under stress.
Reading progress — saved on this device
Algorithmic stablecoins attempt to maintain a reference value using rules, incentives or linked assets that expand and contract supply, rather than relying solely on fully reserved redeemable assets.
What it is
An algorithmic stablecoin uses protocol rules to influence supply or demand around a target price. Mechanisms can include mint-and-burn relationships with another token, bond-like claims, rebase supply changes, automated market operations or combinations of collateral and incentives.
The key analytical question is what ultimately absorbs losses when demand for the stablecoin falls. If the answer depends on issuing more of a volatile governance or secondary token, the system can become reflexive: falling confidence creates more issuance, which weakens the support asset and further reduces confidence.
How it works
A simple two-token design may allow £1 of stablecoin to be redeemed for £1 of a volatile support token. When the stablecoin trades at £0.98, arbitrageurs can buy it cheaply and redeem near £1, contracting stablecoin supply.
The danger is that redemptions mint more support tokens. If stablecoin redemptions are large relative to the support token’s market depth, newly minted support supply can depress its price. More units must then be minted to satisfy the next £1 redemption, creating a potentially accelerating feedback loop.
Rebase designs use a different method: wallet balances can expand or contract so the price target is pursued by changing units held. A stable-looking unit price does not mean a holder’s economic value is stable if the quantity of tokens changes.
Partially collateralised systems may survive stress better when reserves absorb part of the redemption demand, but analysts must distinguish real, liquid collateral from governance tokens or endogenous assets whose value depends on the same system.
How to analyse it
Trace the contraction path. Stability during a premium is often easy because new units can be issued; the difficult question is how the design removes excess stablecoin supply when users want out at the same time.
| Question | Why it matters | What to verify |
|---|---|---|
| What absorbs redemptions? | This determines whether the system has external value backing or reflexive support. | Cash/crypto collateral, endogenous token, auctions or future claims. |
| What happens below peg? | A credible contraction path is essential. | Redemption rule, capacity limits and incentives. |
| How deep is the support-token market? | Thin liquidity amplifies reflexive issuance. | Market depth, concentration and unlocks. |
| Can rules change? | Governance intervention may be required during stress. | Upgrade powers, emergency controls and parameter authority. |
A stablecoin can trade near its peg for a long period without proving the design is robust. The relevant evidence comes from periods of net redemption, shrinking demand and market stress.
Avoid treating market capitalisation of a reflexive support token as if it were cash reserves. Market cap is price multiplied by supply; attempting to sell or mint a large fraction of that supply can move the price substantially.
Worked example and thought exercise
Suppose £100m of stablecoins must be redeemed through a support token trading at £10. The mechanism would need to issue 10m support tokens. If selling pressure pushes that token to £5, the next £100m of redemptions requires 20m newly issued tokens.
If the support market cannot absorb that issuance, the redemption promise becomes progressively harder to honour at the intended economic value. This is a reflexive death-spiral risk, not merely normal volatility.
Thought exercise: If the support token’s market capitalisation is £1bn but only £20m trades daily with shallow depth, how much confidence should you place in the £1bn headline as a redemption backstop?
Common mistakes and practical workflow
- Assuming a long period near peg proves the mechanism is safe.
- Treating support-token market capitalisation as equivalent to liquid reserves.
- Ignoring the difference between expansion mechanics and contraction capacity.
- Grouping partially collateralised and purely reflexive designs together without analysing the loss absorber.
Practical workflow
- Classify the design: collateralised, hybrid, rebase, seigniorage or another mechanism.
- Map what happens when the token trades below target and redemptions rise.
- Quantify external collateral versus endogenous or reflexive backing.
- Compare redemption needs with support-token liquidity and concentration.
- Stress test confidence loss rather than relying on normal-market peg history.
✅ Knowledge checkpoint
- Why is the contraction mechanism more important than expansion during a run?
- How can support-token issuance create a negative feedback loop?
- Why is support-token market cap not the same as reserve liquidity?
- What additional protection can external collateral provide in a hybrid design?
FAQs
❓ Are all algorithmic stablecoins unbacked?
No. Some are hybrid or partially collateralised. The term describes the use of algorithmic stability mechanisms, not one uniform backing model.
❓ Why can mint-and-burn arbitrage fail?
Because the asset received on redemption may lose value or lack enough liquidity to absorb large issuance.
❓ Does a rebase keep holder wealth stable?
Not necessarily. A rebase can change the number of units held even if it targets a stable unit price.
❓ Can governance rescue a failing design?
Possibly, but emergency intervention introduces execution, governance and funding risks and is not guaranteed to succeed.
📋 Summary
Algorithmic stablecoins should be analysed through their loss-absorption and contraction mechanisms. The central risk is reflexivity: if redemption support depends on an asset whose value collapses as redemptions rise, a previously stable peg can fail very quickly.
Want this in a personalised order?
Take the crypto assessment and get a custom path of 10 modules matched to what you already know. Free, no card required.
Build my path →