MM0
Launch

Stress tests

The full maker (strategy, risk engine, executor, accounting, ledger) run through 22 failure scenarios in the simulator. Fail-safe means every invariant held: no risk taken under a blocking condition, no self-trades, no unauthorized transfers, books reconciled.
Fail-safe
22 / 22
ScenarioResultMaker P&LHolding P&LMaker drawdown vs holdingEnd stateBreakers that fired
Token −20% instantlyFail-safe (6 checks)−16.2%−14.0%−3.1%makingextreme volatility
Token −50% instantlyFail-safe (6 checks)−34.4%−27.5%−9.9%circuit breakoracle deviation, extreme volatility
Token −90% instantlyFail-safe (7 checks)−58.5%−45.5%−24.0%circuit breakoracle deviation, max drawdown, max absolute drawdown, extreme volatility, inventory hard limit
Token +500% over two hoursFail-safe (6 checks)+194.7%+220.1%−8.2%circuit breakextreme volatility, oracle deviation, max daily loss, inventory hard limit
Quote stablecoin depegs to $0.93Fail-safe (7 checks)−4.3%−5.0%−0.0%makingextreme volatility, quote depeg
Volume collapses to 2%Fail-safe (5 checks)−5.4%−5.0%−1.1%makinginventory hard limit
Volume 20×Fail-safe (5 checks)+4.4%−5.0%−0.9%defensiveinventory hard limit
80% of external liquidity leaves the poolFail-safe (5 checks)−3.3%−5.0%−0.4%making—
Venue reserves drained 30%Fail-safe (7 checks)−13.3%−5.0%−8.9%circuit breakvenue security incident, max daily loss
Oracle stops updating for 6hFail-safe (7 checks)−4.2%−5.0%−0.9%defensiveoracle stale, inventory hard limit
Oracle diverges from venue by 5%Fail-safe (8 checks)−4.1%−5.0%−0.3%makingoracle deviation, extreme volatility
RPC outage: no transactions land, oracle unreadable (4h)Fail-safe (7 checks)−8.9%−8.6%−0.8%makingoracle stale, execution failure rate, extreme volatility
35% transaction failure rate (24h)Fail-safe (6 checks)−9.9%−9.7%−0.6%making—
Priority fees spike above mandate cap (12h)Fail-safe (6 checks)−6.8%−6.8%−0.4%making—
Steady decline accumulates base to the hard limitFail-safe (6 checks)−20.4%−16.2%−5.2%defensiveinventory hard limit
Token gains a freeze authorityFail-safe (8 checks)−5.0%−5.0%−0.2%circuit breakunsupported token change
Mint authority changes handsFail-safe (8 checks)−5.0%−5.0%−0.2%circuit breakunsupported token change
Venue paused for 3hFail-safe (7 checks)−3.7%−5.0%−0.6%makingabnormal pool state, extreme volatility
AI supervisor unavailable; mandate requires itFail-safe (6 checks)−4.4%−5.0%−0.2%making—
AI supervisor unavailable; mandate allows quant-only safe modeFail-safe (6 checks)−4.0%−5.0%−0.9%makinginventory hard limit
Quant engine unavailable (12h)Fail-safe (7 checks)−13.0%−11.7%−2.0%makingextreme volatility
Unauthorized movement out of the vaultFail-safe (7 checks)−7.7%−5.0%−3.4%circuit breakvault invariant

Fail-safe is about control, not profit. In a sudden crash a concentrated-liquidity maker accumulates the falling token and can lose more than simply holding; the breakers stop new risk but cannot undo fills that already happened.