The DAO · interactive mechanism simulation

Contributors send ETH and receive DAO tokens → holders vote on proposals that pass a curator whitelist and get funded → a dissenting holder can split off a Child DAO. In June 2016, a reentrancy bug let an attacker call the split/withdraw path recursively before the contract zeroed the caller's balance, draining ETH into a Child DAO — trigger it below to see the illustrated exploit and hard-fork clawback.
Contributors send ETH, get DAO tokens DAO Treasury 0.0 ETH · 0 DAO Curators whitelist gate Funded Projects 0 proposals funded Token Holders vote & split Proposals debate period + quorum vote Child DAO 27-day timelock
Contributors joined
0
DAO treasury
0.0 ETH
Proposals funded
0
Child DAO balance
0.0 ETH
Attacker drained (live)
0.0 ETH
Parameters — edit me
1.0/s
55%
10%
25
Controls

Illustrative simulation. Node flows follow the researched mechanism (crowdsale, curator whitelist, proposal voting, split/Child-DAO minority protection), but contribution sizes, vote timing and the exploit burst are randomized and illustrative — not live onchain data, and not the real ~11.5M ETH raised in 2016. Drag the sliders to explore the flywheel, or trigger the reentrancy exploit to see the June 2016 bug and July 2016 hard-fork clawback play out. Part of The Onchain Experiment Atlas.