Kelp DAO Case Study

The Kelp DAO incident taught me how dangerous governance upgrade paths can be. An attacker exploited a contract administration vector and drained a large treasury.

What went wrong

Kelp DAO relied on a multisig upgrade process without sufficient review of the new contract’s access controls. The attacker used a crafted proposal to gain transaction approval.

What I recommend

I always verify both the multisig contract and the upgraded logic. Each upgrade should be reviewed in isolation, with independent auditors checking the final bytecode and signer consensus.

Lessons for teams

Governance is not a substitute for secure primitives. Treat every governance action as an operational security event and use strong separation between proposers and approvers.