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

Decide on governance #168

Closed
5 tasks
liamsi opened this issue Jan 3, 2022 · 2 comments · Fixed by #272
Closed
5 tasks

Decide on governance #168

liamsi opened this issue Jan 3, 2022 · 2 comments · Fixed by #272

Comments

@liamsi
Copy link
Member

liamsi commented Jan 3, 2022

Summary

Currently, we stripped the gov module entirely from celestia-app. We should decide on the gov mechanism if any.

Problem Definition

There is no way to vote on (parameter) changes currently.

Proposal

@musalbas proposed to only have signalling text governance proposals on chain.

The upgrade path must be clearly defined for various scenarios and what role governance should play in this if any.
E.g. should coin holders vote on a block size increase? On upgrading to a new software release? On other params? Only on non-binding signalling text proposals?

Action Items

  • Decide on if we want any governance in the sense of "coin-voting" at all
  • Decide on what kind of proposals governance can vote
  • Summarize findings and decision in a brief ADR
  • then: implement changes in app
  • add a more fine-grained document about various upgrade-paths including what can be voted on but also beyond what is covered by governance

Related:

@liamsi
Copy link
Member Author

liamsi commented Apr 6, 2022

The decision for now:

  • we will add back the full governance module for the next testnet (Add back the governance module #272)
  • if we want to limit anything we should figure this out between testnet and mainnet

IMHO, we should simply use the full governance module at launch. If we ever want to move away from signalling/coin-voting, there either needs to be a governance proposal to do that, or, a coordinated hard-fork. cc @musalbas @adlerjohn

@adlerjohn
Copy link
Member

Sounds good

@adlerjohn adlerjohn linked a pull request Apr 10, 2022 that will close this issue
9 tasks
@liamsi liamsi moved this to Done in Celestia Node Apr 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants