Post
Share your knowledge.
How did they upgrade WMATIC/WPOL contracts without changing addresses?
Hey folks, I've been trying to wrap my head around how the WMATIC to WPOL migration was handled. Specifically, I'm puzzled about how they changed the symbol and name of the contracts 0x0d500B1d8E8eF31E21C99d1Db9A6444d3ADf1270 and 0x0000000000000000000000000000000000001010 when they're not upgradable. How did they manage to keep the same contract addresses but update the immutable contract states? I read some about PIP-45 and noticed something about a network hardfork. Was this change achieved through a hardfork, like it mentions?
- Polygon zkEVM
Answers
2The upgrades for the WMATIC to WPOL migration were indeed achieved through a hardfork, specifically the Ahmedabad hardfork. This process allowed for the changes to be made while keeping the contract addresses the same. You can check out more details about the changes in this GitHub link.
Yes, these kinds of changes typically involve a network hardfork which allows for modifications in the system contracts without altering the actual contract addresses. This method aligns with how network upgrades or changes in immutable contracts are usually handled via governance proposals and subsequent implementations during a hardfork.
Do you know the answer?
Please log in and share it.
Polygon is a decentralised Ethereum scaling platform that enables developers to build scalable user-friendly dApps with low transaction fees without ever sacrificing on security.
