Upgradeability with ZeppelinOS: How Fix Bugs on Deployed smart contracts
summary
ZeppelinOS (OpenZeppelin SDK) provides an upgradeability workflow that uses the proxy pattern so a deployed proxy address keeps storage while the logic contract is replaced; the demo uses the CLI, Ganache, Truffle artifacts and openzeppelin-eth EVM packages to deploy a wallet proxy and an ERC‑20, then pushes a fixed logic contract and updates proxies successfully. Contracts require initialize instead of constructor, storage layout must preserve slots (use reserved storage gaps), and code is served as EVM packages; migrations can run atomically but governance of upgrades is left to the project.
AI-written summary · about
chapters (27)
- 0:00Introduction
- 0:32About Zeppelin
- 2:53Smart Contracts
- 3:53breathability
- 4:35Credibility
- 8:12Removing constructors
- 15:43EVM packages
- 19:08Package contracts
- 20:06Solidity libraries
- 24:56Overview
- 26:20Upgradeable wallet contract
- 27:48Creating a new subunit project
- 29:33Deploying a smart contract
- 30:33Upgrading a smart contract
- 32:51Wallet Initializer
- 35:55Upgradeability
- 39:05Creating a standalone ERC20 contract
- 40:48Creating a traffic console
- 42:13Parameters
- 42:40Request a transfer
- 43:28Upload new contract
- 44:30Update proxies
- 46:00Any questions
- 48:05Example
- 52:05Open Source
- 55:38Alternatives
- 57:33FAQ
related talks
21mScaffold-Eth, OpenZeppelin, and EVM Optimization
22mGetting to Next-Gen Decentralized Governance
16mTips and Tricks to Deploy L1 Smart Contracts on Optimism
25mSmart Contract Developer Speedrun
18mUnderstanding OpenZeppelin Contracts, Defender, and Wizard
20mWhat's New in Scaffold-ETH
01h 03mBeginners Track Welcome & Speedrun Ethereum Introduction
19mTop 5 Tricks for Smart Contract Productivity