Break a vault on mainnet. Watch the contract pay.
One button runs the whole claims path against a vault Rider breaks on purpose: buy cover, push the vault 20% down, open the incident, wait out the confirmation delay, confirm it and pay the policyholder. Every step is a mainnet transaction you can open.
- 01Buy cover
- 02Break the canary
- 03Open the incident
- 04Confirmation delay
- 05Confirm the incident
- 06Pay the policyholder
- 07Claim window
- 08Settle the round
- 09Repair the canary
- 10Rearm the market
Reading the chain…
The vault is a prop. The claim path is the real one.
The canary breaks on purpose
The canary vault is a vault Rider controls. The drill moves 20% of its USDC out, and its trigger reads the share-price drop exactly as the live triggers read a Morpho vault.
It sells to the drill runner only
The canary market refuses every other buyer on-chain, so nobody can buy cover on a vault that is about to be broken. The refusal, mined ↗
A separate pool pays
Drill claims come out of the drill pool, fenced off from the underwriting pool. No underwriter's capital ever pays for a drill, and only Rider's deployer can fund it.
Rounds are rate-limited
A relayer pays the gas in USDC so nobody needs a wallet. New rounds are capped per day and pause if the relayer runs low. A round that has started can always finish, so anyone can pick up a half-run one.
Everything else is production: the same market contract, the same policy NFT and the same claim code as the four live markets. Which step comes next is read from chain state, not from a database, so every visitor sees the same drill.
- Buy canary cover (approve + buy, one Multicall3From tx)0x4588fea0…329c24 ↗
- Break the canary vault (-20%)0xc0b9a03a…5c6e37 ↗
- Open incident0xb73f9be0…094345 ↗
- Confirm incident after the delay0x995ec5ad…4c0856 ↗
- Pay the policyholder0xf3aba7fb…a11474 ↗