4

Can the EVM update deprecate operations of older smart contracts, making these contracts non-operative? If so, what are the solutions to upgrade these smart contracts to the new version of the EVM if they cannot be modified directly (due to immutability)?

| improve this question | |
  • 2
    Possible duplicate of Upgradeable smart contracts – Richard Horrocks Jul 10 '17 at 18:03
  • This is a corollary of the question you flagged as duplicate. This one relates to the situation where the contract owner does not wish to upgrade the contract. This question is: will an upgrade to the platform force the owner to upgrade (or deprecate, or delete) the contract. – dcorking Jul 11 '17 at 11:52
2

Yes, and in fact some already have in the past due to changes to the gas schedule.

Designing a contract to be upgradeable like xgabrielx said is a good practice due to unforeseen changes and problems like this.

| improve this answer | |
1

Well yes, over time some functions might be depricated (as is standard procedure, not limited to EVM).

(1) You deploy a new contract, telling users to start using that instead.

(2) You have a fronting contract which points to the "latest" version of you main contract.

(3) Use ENS to mycontract.eth and point it to the latest version of your contract.

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.