https://github.com/decentralisedme/upgrades
Example of how Proxies can be use in order to "upgrede" an existing smart contract. Interesting to see how all the txns are performed via Proxy, there is no trace on the implemented smart contracts
https://github.com/decentralisedme/upgrades
Last synced: 6 months ago
JSON representation
Example of how Proxies can be use in order to "upgrede" an existing smart contract. Interesting to see how all the txns are performed via Proxy, there is no trace on the implemented smart contracts
- Host: GitHub
- URL: https://github.com/decentralisedme/upgrades
- Owner: Decentralisedme
- Created: 2022-06-13T17:47:53.000Z (about 4 years ago)
- Default Branch: main
- Last Pushed: 2022-06-13T18:05:33.000Z (about 4 years ago)
- Last Synced: 2024-12-30T12:27:07.699Z (over 1 year ago)
- Language: Solidity
- Homepage:
- Size: 6.84 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
Lesson 12 from PatrickAlphaC:
- https://github.com/smartcontractkit/full-blockchain-solidity-course-py
Two contracts have been created:
1. Box >> retrieve and store functions
2. BoxV2 >> retrieve, store and increment functions
We want:
1. deploy Box
2. store some value
3. Upgrade From Box => BoxV2
4. Increment the already stored value
This is peroformed via OpenZeppelin proxy contracts:
- ProxyAdmin
- TransparentUpradeableProxy
The contracts have been deployed and verified in Rinkeby and as result Upgrade + Store + Increment have all been done via proxy, as you can see:
- https://rinkeby.etherscan.io/address/0x13ff473c6253966a6b3454e0c00ab70f14470e6f
Tests have been run as well.