Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

(feat) migration tooling for sway upgrades #268

Open
3 tasks
DefiCake opened this issue Sep 3, 2024 · 0 comments
Open
3 tasks

(feat) migration tooling for sway upgrades #268

DefiCake opened this issue Sep 3, 2024 · 0 comments

Comments

@DefiCake
Copy link
Member

DefiCake commented Sep 3, 2024

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant