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
We must have tooling that fills, even if just approximately, the same roles the openzeppelin-upgrades and hardhat-deploy plugins do for solidity contracts.
Currently, the plugins do this (non-exhaustive list):
Keep track of deployed proxy addresses, their implementations and the arguments with which they are deployed, per chain
Keep track of storage layouts for each implementation, so that attempts to upgrade to contracts that do not have the same storage pattern are flagged
Allow to do "async" style upgrades so that they can be prepared with a transaction payload and executed with multisigs at some other time.
I am not sure how to proceed with this. I think we could leverage some of the existing solidity tooling, but only partially, if we integrated packages/fungible-token and packages/solidity-contracts under a single package, say contracts, but I have not thought about a roadmap
The text was updated successfully, but these errors were encountered:
We must have tooling that fills, even if just approximately, the same roles the openzeppelin-upgrades and hardhat-deploy plugins do for solidity contracts.
Currently, the plugins do this (non-exhaustive list):
I am not sure how to proceed with this. I think we could leverage some of the existing solidity tooling, but only partially, if we integrated
packages/fungible-token
andpackages/solidity-contracts
under a single package, saycontracts
, but I have not thought about a roadmapThe text was updated successfully, but these errors were encountered: