You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
All the examples make it look like to upgrade a contract, you are changing the proxy to a new implementation address whose Contract name is different from the old implementation. (BoxV2 against Box).
But how do you make changes to the old implementation without changing its name and successfully upgrade the proxy?
For example, you fix a simple logic in one line of code in Box and then you want the proxy to reflect this. But then following the provided steps don't work. Even after setting unsafeSkipAllChecks to false in opts.
So how do you upgrade without changing name?
The text was updated successfully, but these errors were encountered:
You could use the same contract name in a differently named Solidity file, then refer to that contract using its fully qualified contract name in the format FILE_PATH:CONTRACT_NAME. For example, "contracts/BoxV2.sol:Box"
The purpose of requiring both versions of the contract is to allow storage layout validations to be run.
All the examples make it look like to upgrade a contract, you are changing the proxy to a new implementation address whose Contract name is different from the old implementation. (BoxV2 against Box).
But how do you make changes to the old implementation without changing its name and successfully upgrade the proxy?
For example, you fix a simple logic in one line of code in Box and then you want the proxy to reflect this. But then following the provided steps don't work. Even after setting
unsafeSkipAllChecks
to false in opts.So how do you upgrade without changing name?
The text was updated successfully, but these errors were encountered: