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

Migrating AppProxies to different appIds #548

Open
sohkai opened this issue Aug 5, 2019 · 0 comments

Comments

@sohkai
Copy link
Member

commented Aug 5, 2019

Currently, AppProxies are assigned an appId that is assumed to never be changed.

While this has so far made it easy to validate an AppProxy's deployment and simplified various points of implementation, it has the drawback of making it impossible to migrate an AppProxy from using an app on one aragonPM registry to another.

A common usecase is a new app being published on an experimental registry, e.g. open.aragonpm.eth, and then later being improved and moved into the main registry, aragonpm.eth. Users of the original experimental app have no way, outside of uninstalling and reinstalling an app, to migrate to the improved version on the main registry.


One potential implementation path is to modify both the Kernel and AragonApp:

  • Kernel: expose a method, protected by APP_MANAGER_ROLE, that calls a method to change an appId on a given proxy
  • AragonApp: expose a method, callable only by the connected kernel, that changes the internal appId
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant
You can’t perform that action at this time.