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

Proxy migration for future versions #17

Open
Art3miX opened this issue Mar 31, 2023 · 0 comments
Open

Proxy migration for future versions #17

Art3miX opened this issue Mar 31, 2023 · 0 comments
Labels
🔮 the future 🔮 issues that we should consider now that may emerge later.

Comments

@Art3miX
Copy link
Collaborator

Art3miX commented Mar 31, 2023

Context discussion here

While Note and Voice are singleton contracts per a link (chainA -> ChainB) and they can be migrated when needed in one "cheap" action, proxy contracts are created per account used, so those cannot be migrated in 1 action without unreasonable gas fee.

While at the moment proxy contracts are simple and probably will not contain any major upgrades/migrations in the near future, there might come a point in time we will need to consider it.

One way of doing this is to add logic to Voice where it does a check if account/proxy needs an upgrade, if it does, it first does the migration of the account, and only then dispatch the msgs, this ensures the migrations of the proxy only happens on active accounts and reduce "expenses" to bare minimum.

@0xekez 0xekez added the 🔮 the future 🔮 issues that we should consider now that may emerge later. label Apr 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🔮 the future 🔮 issues that we should consider now that may emerge later.
Projects
None yet
Development

No branches or pull requests

2 participants