Intermediate
Proxies & Upgradeable Contracts — Check your understanding
Understand how upgrades work.
Developer Intermediate
6/6 — Proxies & Upgradeable Contracts — Check your understanding
Readiness If you cannot describe your storage layout rules, who can upgrade, and how to roll back, you are not ready for mainnet. Tighten until you can.
The root problem with conventional currency is all the trust that’s required to make it work.
Proof points You should have storage diff tests, unauthorized-upgrade tests, and a documented admin rotation plan. You should know where events/changelogs live.
Communication Be prepared to explain to users what an upgrade does, how you mitigate risk, and how they can verify the new implementation.
Key points
- Explain why constructors don’t:Run behind proxies and show your initializer guard.
- Describe a storage collision:Scenario and how your append-only layout + gaps prevent it.
- Contrast Transparent vs UUPS:Vs Beacon and when to choose each.
- Show how to rotate/lose:An upgrade admin safely (multisig/timelock) and recover from mistakes.