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
The reasons for not introducing support for upgradable contracts at present are as follows:
At first, We are currently in the development and testing phase, where incompatible upgrades will be made. Therefore, to prevent potential bugs due to compatibility issues (such as configuring new version mining software on old version contracts), we intentionally do not support contract upgrades. (I have been tortured too many times by the DLL hell of the past in Windows)
The second reason is due to the complexity of the contract logic, we are still uncertain about how many contracts will collaboratively complete the entire logic. Therefore, which contracts are upgradable and which are not, still need further discussion.
When we decide to move to a stable version and start introducing support for upgrades, I plan to initiate a discussion about who can operate the upgrades and which features can be upgraded. Thank you very much for your attention and support.
Current version is not upgradable meaning when we realize there is a caveat, we can't make change. I suggest we consider upgradability
https://docs.openzeppelin.com/upgrades-plugins/1.x/proxies
The text was updated successfully, but these errors were encountered: