Unit 4 · Level 3 · The DeFi risk stack
Governance & admin keys
'Decentralized' is a spectrum, not a badge. Many protocols keep an admin key or a small multisig that can upgrade the very contracts holding your money. That's convenient for fixing bugs and terrifying if stolen or misused. Others hand control to token-holder votes, which just moves the question: who owns the votes? Before depositing, always ask the least glamorous question in DeFi: who can change the rules, and how fast?
Free to play. No ads, no token, no account needed to start.
What you get asked
Why do admin keys matter to you as a depositor?
An upgradeable contract is only as trustworthy as its upgraders. If one leaked key can swap the code, your 'trustless' deposit trusts that key completely.
A protocol upgradeable by a 2-of-3 ___ is only as safe as those three keyholders.
A multisig needs several signatures to act. That's better than one key, but two compromised laptops out of three is still game over.
Match each governance setup to its trade-off:
Each design trades safety for flexibility differently. A long timelock is the depositor's best friend: whatever changes, you get a head start.
How does a 'governance attack' work?
Votes are just tokens, and tokens can be bought, or even flash-loaned. Beanstalk lost roughly $180M in 2022 to a proposal passed with borrowed voting power.
Before depositing, the governance question worth answering is:
Marketing says 'decentralized'; the contract's admin settings tell the truth. Read the boring part; that's where your risk lives. 🐜
The rest of this unit
Code, oracles, and admin keys: the risks stacked under every APY.