Crypto-Collateralised Stablecoins
Understand crypto-collateralised stablecoins, overcollateralisation, liquidations, oracle dependencies and reflexive collateral risks.
Reading progress — saved on this device
Crypto-collateralised stablecoins are created against on-chain collateral rather than conventional fiat reserves, usually using overcollateralisation and automated liquidation rules to protect the stablecoin’s solvency.
What it is
A user typically locks eligible cryptoassets in a smart contract and borrows or mints stablecoins against that collateral. Because the collateral is volatile, the protocol usually requires collateral value to exceed the stablecoin debt by a meaningful margin.
If the collateral ratio falls below a protocol threshold, liquidation mechanisms attempt to sell or transfer collateral so the system can repay stablecoin debt. The design shifts key risks from bank and issuer balance sheets toward collateral quality, smart contracts, oracles, market liquidity and governance.
How it works
Assume a user locks £15,000 of collateral and mints £10,000 of stablecoins. The initial collateral ratio is 150%. A 25% collateral-price fall reduces collateral value to £11,250 and the ratio to 112.5%, potentially below the protocol’s liquidation threshold.
Liquidation must occur before collateral value falls beneath the debt plus liquidation costs. That requires timely oracle updates, available liquidators and enough market depth. During a fast crash or network congestion, liquidation discounts and execution delays can create bad debt.
Collateral concentration matters. A system advertised as “crypto-backed” may rely heavily on one volatile token, liquid-staking asset, wrapped asset or even other stablecoins. Correlated collateral can fail together, weakening diversification precisely when it is needed.
Some systems use governance or protocol reserves to absorb shortfalls. Those backstops can improve resilience but add governance, dilution or treasury risk. The economic safety of the stablecoin therefore depends on the whole liquidation and recapitalisation stack, not merely the initial collateral ratio.
How to analyse it
The key analytical task is stress testing. Ask not only whether the system is overcollateralised now, but whether collateral can be valued and liquidated quickly enough through a severe market move.
| Question | Why it matters | What to verify |
|---|---|---|
| What is accepted collateral? | Volatility, liquidity and correlation drive liquidation risk. | Collateral mix, concentration and wrapped/bridged dependencies. |
| How is collateral priced? | Liquidation decisions depend on reliable valuations. | Oracle design, update cadence and fallback mechanisms. |
| How are positions liquidated? | Slow or thin liquidation markets can create bad debt. | Auction/AMM design, penalties, keeper incentives and capacity. |
| Who changes parameters? | Risk settings can be altered by governance or administrators. | Governance process, emergency powers and timelocks. |
Published collateralisation ratios can hide distribution. A protocol may be 180% collateralised in aggregate while a large cohort of individual vaults sits close to liquidation.
Also separate collateral value from collateral liquidity. A token worth £500m at spot prices is not necessarily liquid enough to absorb a £100m forced sale without substantial market impact.
Worked example and thought exercise
A protocol has £1bn of stablecoins outstanding and £1.6bn of collateral, implying 160% aggregate backing. However, £900m of collateral is the same volatile asset and £250m of positions would be liquidated if that asset falls 15%.
If market depth can absorb only £50m near current prices, the system can face slippage and bad debt despite appearing comfortably overcollateralised before the shock. Aggregate ratios are therefore a starting point, not a complete solvency test.
Thought exercise: Which would you rather know during a crash—the protocol-wide ratio or the size of collateral that must be sold within the next 5% price move?
Common mistakes and practical workflow
- Assuming on-chain collateral automatically means low counterparty risk.
- Looking only at aggregate collateralisation and ignoring position-level liquidation clusters.
- Ignoring oracle, smart-contract and liquidation-market dependencies.
- Treating all collateral at quoted market value as immediately realisable at that price.
Practical workflow
- Map the collateral types, concentrations and external dependencies.
- Inspect liquidation thresholds and the distribution of vault health.
- Review oracle design and failure contingencies.
- Stress test collateral prices and available liquidation liquidity.
- Identify governance or recapitalisation mechanisms for residual bad debt.
✅ Knowledge checkpoint
- Why can a 160% aggregate collateral ratio still be fragile?
- What happens if an oracle is stale during a rapid collateral decline?
- Why is collateral liquidity different from collateral market value?
- How can correlated collateral undermine an apparently diversified system?
FAQs
❓ Why is overcollateralisation needed?
Because crypto collateral is volatile; the buffer is intended to absorb price declines before debt becomes undercollateralised.
❓ Can a crypto-collateralised stablecoin still depeg?
Yes. Liquidation failures, confidence shocks, oracle problems and imbalance between minting and redemption can all affect price.
❓ Does on-chain transparency eliminate governance risk?
No. Governance may control collateral eligibility, liquidation parameters, fees and emergency actions.
❓ What is bad debt?
Stablecoin debt that remains after available collateral and liquidation proceeds are insufficient to cover the obligation.
📋 Summary
Crypto-collateralised stablecoins replace much of the conventional reserve structure with on-chain collateral and liquidation mechanics. Their resilience depends on collateral quality, oracle accuracy, liquidation capacity and governance under stress—not simply on a headline collateral ratio.
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 →