-
Notifications
You must be signed in to change notification settings - Fork 43
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
Update "Deploy Linked Token" GH action to support Proxy upgrade pattern #854
base: main
Are you sure you want to change the base?
Conversation
…ation instance of the same code and pretter
…pyard/ipc into mikers/linkedTokenUpgrades
@maciejwitowski that assumption is correct. I was optimistically working on this and it's also turning into a large time sync. The code has a dependency on a server that I don't know the details about, takes a long time to run so it's hard to test, and seemed to have quirks that I haven't gotten deep into where it would be flaky - I think due to multiple runs of tests happening a time. For now I had just left it but do not have a clear plan because of the cost benefit analysis on how much time to fix vs how much its worth fixing. |
@consensus-shipyard/ipc-core-devs I would suggest to close the issue as it is not something critical and it does not work. |
This PR adds support for proxy upgrades to the linked_token_deployment branch which is now in Main.
Currently the check makes it to
make deploy-replica-proxy
and then fails with the error:next step to investigate that is to see if the account sending transactions related to the linked token is separate from an ipc validator and to make it its own funded account if it is not
This change is