Governance Taxonomy
A taxonomy of governance events and their associated metrics
Status
To track proposals, every proposal in Messari Governor has an attached status to it. Below are the definitions of each status:| Status | Definition |
|---|---|
| Preliminary Discussion | The proposal is currently being discussed by the community but has not been submitted for a vote. |
| Upcoming Vote | The proposal has been submitted by a vote (off-chain or on-chain) that has not started yet. |
| Active Vote | The proposal is currently being voted on (off-chain or on-chain). |
| Succeeded | The proposal has succeeded. For some proposals, this will be the terminal state, as they don’t require any form of execution. For others, the proposal will then be queued for execution. |
| Queued | The proposal has been queued for execution and will be executed on-chain. |
| Failed | The proposal has failed. This can happen if the quorum hasn’t been reached or if the choice for the proposal to succeed hasn’t gathered enough votes. |
| Canceled | The proposal has been canceled. This can happen at all stages of the proposal life-cycle. |
| Executed | The proposal has been executed on-chain. |
| Pending Analysis | This happens when a proposal has been voted on Snapshot and the snapshot vote is now closed. This requires human intervention to know if the proposal has succeeded or failed, if there will be another vote, an on-chain execution, or not. |
Categories and Subcategories
Each proposal in Governor has one assigned category and sub-category. After selecting a category, the connected sub-categories will only be available.| Category Name | Available Subcategories | Examples |
|---|---|---|
| Funding | Equity Funding, Debt Funding, Public Token Sale, Private Token Sale | Project closes equity funding round, Project closes debt funding round, Project sells token to public/ICO/IDO, Project sells token not available to public |
| Governance | Governance Update, Other Network Change | Project governance process is changed, DAO/voting council election/elected, Polkadot parachain auctions |
| Integration | Scaling Solution Integration, Cross-Chain Bridge Integration, Oracle Integration | A project integrates a scaling solution, a bridge, or an oracle |
| Parameter Change | Fee Parameter Change, Collateral Parameter Change | Fee parameter is changed on application, Collateral parameters are changed |
| Release | Core Client Release, SDK Release, On-Chain Upgrade, Contract Deployment, On-Chain Upgrade, Other Network Change | Application releases upgraded contracts, Governance Vote to enable chain upgrade, Vulnerability is patched in Core client |
| Security | Report, Fork, Mining and validation, Treasury Funded Expense, Bug Bounty Program | A security audit of a protocol has been published, A protocol is forked to patch a vulnerability, Bounty Bounty Program is launched |
| Team and Operations | Treasury Funded Expense, Project Team, Grant Program, Report, New Brand or Rebrand, Call or Meeting, Other Project Change | Projects spend treasury funds, team funding |
| Token Supply | Airdrop, Treasury Funded Expense, Liquidity Mining Program, Treasury Funded Expense, Mining and Validation, Grant Program, Supply Unlock, Supply Lock | A portion of the token supply has been allocated for a grant program, A portion of the protocol’s native token supply is locked and no longer freely transferable, Tokens vest/tokens are unlocked |
| Token Type | New Supported Asset, New Collateral Asset, New Token, Airdrop, Token Swap, Other Token Change | The application adds new asset support, Lending app adds new collateral asset, Project launches new native token |
Importance
The importance level is set based on the impact a certain proposal may have on the protocol, or the token holders of the native asset of the protocol. The available importance levels are listed below:| Importance | Definition |
|---|---|
| Low | Includes proposals where no action is needed, no strong impact on stakeholders or the DAO itself, or the day-to-day DAO operations recurring proposals. Some examples are team payroll changes and small parameter updates |
| Medium | Includes proposals that engage substantial spending from a DAO, significant parameter changes, or uncommon decisions that are voted on but don’t deeply impact the DAO or stakeholders. Some examples are DAO budget approval, small changes in tokenomics, or the governance process or structure |
| High | Includes proposals that engage significant spending from a DAO, major changes in the DAO structure or smart contracts, or exceptional proposals stakeholders should be aware of. Some examples are tokenomics revamp, on-chain upgrades, and important DAO expenses |
| Very High | This is rarely used but should be used when an issue directly impacts stakeholders or the DAO, particularly if it is a time-sensitive proposal. Some examples are hack-related proposals and DAO mergers |
Sentiment Levels
Sentiment gauges interest in the proposal during the preliminary discussion phase. The sentiment level is based on the number of answers, the community members that participate in a given discussion, and their explicit support of the proposal. Listed below are the available ‘Sentiment Levels’:- Negative
- Neutral
- Positive
- Very Positive