Drift Protocol · liquidity & admin-risk simulation

Every taker order routes through a priority stack: a JIT Dutch auction first, then a keeper-run orderbook, then the oracle-anchored DAMM as backstop. Filled trades settle into the cross-margin vault, backstopped by a staked insurance fund. Try the exploit button to see why the 2026 loss was an authority failure, not a liquidity-mechanism failure.
Traders taker orders JIT auction 5s Dutch, maker fills fill rate 55% Market makers fill at/better than DAMM DLOB keeper-matched orderbook DAMM backstop Cross-margin vault $0 TVL Insurance fund $0 staked Security council ADMIN COMPROMISED multisig admin key
Orders routed
0
Vault TVL
$0
Insurance fund
$0
Filled via
JIT 0 · DLOB 0 · DAMM 0
Parameters — edit me
55%
60%
$5,000
1.8/s
Controls

Illustrative simulation. Models Drift v2's routing priority (JIT auction → DLOB → oracle-anchored DAMM backstop) and its insurance-fund waterfall. The exploit button illustrates the April 2026 incident: attackers social-engineered Security Council signers into pre-signing durable-nonce transactions, seizing admin control and draining the vault in seconds — a governance failure, not a flaw in the liquidity mechanism. Trade sizes and timing are randomized for visualization, not live onchain data. Part of The Onchain Experiment Atlas.