The Autonomous Fund Needed a Human Rescue

1. A virtual organisation

The DAO raised ether through token sales to fund projects. Software and token-holder voting were intended to coordinate an investment organisation. The project aimed to coordinate funds through published software rules. Putting those rules into code did not guarantee the code behaved safely.

The structure depended heavily on what its code allowed.

2. The rules are also software

A project can publish its intended rules while still depending on code whose behavior is difficult to anticipate completely. That creates a gap between what participants believe an arrangement will do and what execution can actually permit. The DAO exposed that gap in a setting where the rules were directly connected with substantial funds.

Visibility had not guaranteed correctness.

3. Warnings emerge

Concerns about code vulnerabilities appeared before the attack. Proposed safeguards and a temporary pause were discussed. A weakness in execution could matter even with publicly visible software. Transparency and correctness are not the same property.

The warning period did not finish before the danger arrived.

4. The diversion

On 17 June 2016, an unknown attacker began diverting ether. Approximately 3.6 million ether moved into an attacker-controlled address. The diverted funds created a dispute about how the community should respond. Technical possibility did not by itself settle the preferred outcome.

The programme had followed a path its backers did not want.

5. The fork

Developers and other participants supported a change to Ethereum’s protocol. In July, an adopted hard fork enabled a recovery arrangement for DAO token holders. A change accepted by some participants could be rejected by others. The network's history therefore involved people making competing decisions.

An autonomous experiment required a collective human decision.

6. People decide what to preserve

After the diversion, the community faced a decision that no simple claim about code could resolve for everyone. Different participants valued continuity and intervention differently. The resulting choices showed that a technical network still had a human history, where agreement about how to respond could divide even people using the same original system.

The program had created a political question.

7. The record

The SEC later examined the offering and its investment structure. The incident exposed technical and organisational assumptions behind a supposedly self-operating fund. The split left a record of both technical failure and governance. A programmed system still operated within a human community.

Writing rules in code had not removed the need for governance.

Sources

• SEC — Original DAO investigation report