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.

Sign up for GitHub

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

Jump to bottom

Add more approaches for user upgradeability governance #15

Open
maraoz opened this issue Feb 2, 2018 · 0 comments
Open

Add more approaches for user upgradeability governance #15

maraoz opened this issue Feb 2, 2018 · 0 comments
Labels
kind:research Research on a topic before implementing it topic:governance zOS governance and token mechanics
Milestone
Backlog

Comments

@maraoz
Copy link
Contributor

maraoz commented Feb 2, 2018 •
edited
Loading

Currently, the only method for upgrading a new version of code is through a centrally controlled owner.

Research alternative to OwnedUpgradeabilityProxy
@maraoz maraoz added the kind:research Research on a topic before implementing it label Feb 2, 2018
@spalladino spalladino changed the title new approach for upgradeability governance: based on vouching New approach for upgradeability governance: based on vouching Feb 20, 2018
@spalladino spalladino added the topic:governance zOS governance and token mechanics label Feb 20, 2018
@maraoz maraoz added this to the v0.1.0 (Kernel MVP) milestone Mar 7, 2018
@maraoz maraoz changed the title New approach for upgradeability governance: based on vouching Add more approaches for user upgradeability governance Mar 16, 2018
@maraoz maraoz modified the milestones: v0.1.0 (Kernel MVP), v0.2.0 Mar 16, 2018
@facuspagnuolo facuspagnuolo modified the milestones: v2.0.0, Backlog Jun 7, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind:research Research on a topic before implementing it topic:governance zOS governance and token mechanics
Projects
None yet
Milestone
Backlog
Development

No branches or pull requests
3 participants
@maraoz @spalladino @facuspagnuolo