Open cygnusv opened 1 month ago
This is a known design flaw when handling upgradeable contracts. Ape keeps a cache of deployments that is used as a way to lookup deployment details of a previously deployed proxy contract. However, if there is more than one entry in this ape cache we do not have any means of disambiguating which deployment instance the user is trying to interact with. Instead of accepting the additional complexity of disambiguation we decided to raise this error instead.
Workaround is to rm -rf ~/.ape/
/, but there has to be a better way!
This is the most simple solution and It can even be adopted as a long-term solution by automating the deletion of specific cache entries. It's acceptable to just delete it since we're using our own deployment metadata tracking system instead of ape's. The effort vs. benefit of trying to wrap the cache with additional context is not good imo.
Related to https://github.com/nucypher/nucypher-contracts/issues/143
Workaround is to
rm -rf ~/.ape/<NETWORK>/
, but there has to be a better way!