All my token storages changed to zero after the implementation

[JohnnL]

I have a ERC20 token deployed using the ERC196 Proxy using open-zeppelin contracts (Initializable, UUPSUpgradeable, OwnableUpgradeable, etc).

The problem is, the last implementation upgrade occurred 480 days ago (version 4.4.1). My team needed to update the code again and I imported the open-zeppelin contracts in remix.ethereum.
I think that open-zeppelin contracts received some updates (version 5.0.0) and some storages changed. Given this, we updated the implementation and all slots were reseted. The owner, totalsupply, proxyUuid, etc. Everything is with 0 value and I can't upgrade it again to the old implementation.

Is there something I can do?

[ernestognw]

Hey, you can find more about backwards compatibility in our documentation:

Backwards Compatibility - OpenZeppelin Docs

From what I read, sounds like the storage layout shifted and you’re probably not the owner of the contract or authorized to perform upgrades.

Please feel free to reopen but provide relevant addresses or code along with your question.

How do I ask a good question?

If you were redirected here, your post did not meet quality standards. Please review this page and edit or create a new topic according to the guidelines. Asking good questions is important in this community. It will improve your chances of getting an answer from the OpenZeppelin team or community members, and of finding out how to solve your problem. Users are expected to put in a minimum level of effort. Topics will be closed unanswered if moderators consider that this was not the case. Re…