Proposal
A question or change is written in a form that others can inspect.
Governance notes for decentralized protocols
Governance is the set of processes through which a protocol proposes, reviews, adopts, and explains changes. It can involve technical contributors, operators, delegates, researchers, and a broader community. Pequet describes governance as an object of study, not as a signal to acquire or participate in any asset.
Review
Participants test assumptions, identify consequences, and request clarification.
Adoption
A decision is implemented through the rules and software of the protocol.
Rules are also infrastructure
A governance change can affect validator software, hardware requirements, monitoring procedures, delegation arrangements, or the interpretation of an incident. The change may be technically small while creating operational work for many participants.
Good analysis follows the path from proposal to implementation. It asks who can submit a change, who can review it, how a decision is recorded, when software is released, and how operators learn what they need to do.
- Read the proposal and supporting rationale.
- Identify affected roles and systems.
- Check the implementation and communication timeline.
Governance process overview
| Stage | Primary question | Useful evidence |
|---|---|---|
| Submission | Who may raise the issue? | Proposal format and authorship record |
| Discussion | What assumptions are challenged? | Public comments and technical reviews |
| Decision | How is support measured? | Voting or decision record |
| Implementation | What changes in practice? | Release notes and operator guidance |
| Follow-up | Did the change behave as expected? | Incident, performance, or review notes |
Questions that improve a proposal review
- What problem is the proposal trying to solve?
- Which users, operators, or applications may be affected?
- What assumptions are supported by data and which remain speculative?
- What happens if adoption is partial or delayed?
- How will the result be reviewed after implementation?
These questions do not decide an outcome. They make the decision record easier for readers to understand later.
“A transparent decision is not one without disagreement; it is one where the question, evidence, process, and result can be inspected.”
Explore related material in staking protocols and research notes.