Azuro Protocol · interactive mechanism simulation

Bettors route stake through frontend apps into one shared LiquidityTree pool. Data providers seed odds; the vAMM prices bets; losing stakes become LP yield (split with frontends), winners get paid straight from the pool.
Bettors stake on outcomes 1.5 bets/s Frontend apps 30+ betting UIs (affiliates) 30% of margin LiquidityTree Pool singleton, per-LP share tracking 200.0 ETH TVL Data providers seed & resolve odds 5% house margin LPs deposit / withdraw 1.0 ETH avg stake Open bets AzuroBet NFTs, awaiting result AzuroDAO elects providers, arbitrates disputes
Bets placed
0
Pool TVL
200.0 ETH
LP yield accrued
0.0 ETH
Frontend revenue paid
0.0 ETH
Open bets (NFTs)
0
Parameters — edit me
1.5/s
5.0%
30%
1.0 ETH
Controls

Illustrative simulation. Defaults mirror the researched Azuro mechanism (singleton LiquidityTree pool, data-provider-seeded vAMM odds, AzuroBet NFTs, frontend affiliate revenue share) but bet sizes, timing and outcomes are randomized for visualization — not live onchain data. The "stale-odds exploit" button dramatizes Azuro's real weak point: whitelisted data providers are a semi-permissioned trust point that sharp bettors can exploit before AzuroDAO can resolve a dispute. Drag the sliders to explore how the flywheel responds. Part of The Onchain Experiment Atlas.