Repository navigation
Q. DAO Proposal and Voting Guide
This guide explains how to create, review, vote on, finalize, and execute proposals in Diamond UI. For proposal types, voting thresholds, governance parameters, and cycle rules, see DAO Governance.
On this page
- Getting Started
- Creating a Proposal
- Proposal-Specific Fields
- Reviewing and Voting on Proposals
- Finalizing and Executing Proposals
- Following Governance as a Delegator
Open the DAO section of Diamond UI Mainnet and connect a compatible wallet to the intended DMD network. Keep enough DMD available for transaction fees and, when creating a proposal, the proposal fee displayed by the interface. For wallet setup, see Diamond UI User Guide and Wallet Compatibility.
Anyone can submit a proposal during the proposal phase; owning a validator pool is not required. Validator pool owners vote using their pool's DAO voting weight, which includes their own stake and delegated stake. Voting is not limited to the active validator set. Operating a validator node does not automatically grant voting rights.
- During the proposal phase, open the DAO page and select Create Proposal.
- Select the Proposal type.
- Enter a clear Proposal Title and Description explaining the requested action and its purpose.
- Complete the fields required for the selected proposal type, as described below.
- Add a Discussion URL, if relevant, so participants can review supporting discussion.
- Review the proposed outcome, voting rule, proposal fee, and estimated transaction fee shown by the interface.
- Select Create Proposal, confirm the transaction in your wallet, and check that the proposal appears in the DAO list.
The proposer can dismiss a proposal during the proposal phase. Dismissal does not refund the proposal fee. Fee handling and governance timing are described in Proposal Lifecycle and Fees.
The following names match the proposal-type selector in Diamond UI.
| Proposal type | Information to provide |
|---|---|
| Open Proposal | Describe the initiative. For a funding request, specify each recipient's externally owned account (EOA) address and the amount of DMD requested. Multiple recipients can be included. Review the funding source and corresponding voting rule shown by the interface. An Open Proposal can also be submitted without a payout. |
| Ecosystem parameter change | Select the parameter and choose a value from the predefined range. Explain the reason for the change. See Governance Parameters for the parameter definitions and limits. |
| Contract upgrade | Provide the target contract address and encoded calldata for the intended action. Follow the Contract Upgrade Proposal Guide to prepare and verify the contract call. |
| Low Majority Balance Fill | Specify the amount of DMD to transfer from the Governance Pot to the Low Majority Contract. This is a subtype of Contract Upgrade proposal. |
| Username Moderation | Enter the username, its owner address, and a reason category. Explain the request in the description and optionally provide evidence or notes. This corresponds to DAO Names Moderation in DAO Governance. |
- Open an active proposal from the DAO list during the voting phase.
- Review the title, description, proposer address, and any discussion link. Check the specific action: payout recipients and amounts, a parameter and its proposed value, a target contract and calldata, or the username and moderation evidence.
- Review the required Participation and Exceeding Yes thresholds. Both must be satisfied; Exceeding Yes is not simply the share of participating votes that support the proposal. See Voting Weight and Approval Thresholds for the calculation.
- Connect the wallet associated with your validator pool's voting rights, select For or Against, and confirm the transaction.
- Check that your vote is recorded and monitor the proposal's voting results.
During voting, a recorded vote can be changed to the opposite choice, but it cannot be removed. You can review validator votes on the proposal page or use the Validator Candidate Participation Table on the validator page.
Finalization records the voting result. Execution carries out an approved proposal's action. These are separate steps.
On the DAO page, the Actions Needed tab lists proposals awaiting finalization or execution. Approved proposals remain available for execution until the execution period ends. These proposals can also be found in History Proposals.
After voting ends, find the proposal in Actions Needed or History Proposals and use Finalize. Confirm the transaction in your wallet and check the resulting status.
Anyone can finalize a proposal. All proposals from the previous voting phase, whether accepted or rejected, must be finalized before new proposals can be created. For an accepted proposal, the proposal fee is refunded to its creator at finalization. The fee for a rejected proposal is transferred to the Reinsert Pot.
For an accepted, finalized proposal, find it in Actions Needed or History Proposals, review the approved action, and use Execute while it remains available. Confirm the transaction and check that execution succeeds.
Open Proposals and Ecosystem Parameter Change proposals can be executed by anyone. Contract Upgrade proposals require the original proposer to initiate execution; follow the Contract Upgrade Proposal Guide for the technical workflow.
Execution must occur within the following proposal-and-voting cycle. Once that window expires, the proposal can no longer be executed. Unexecuted proposals do not prevent a new governance cycle from proceeding. See Proposal Lifecycle and Fees for cycle durations and execution rules.
If multiple approved proposals change the same governance parameter, coordinate which one will be executed within the applicable parameter-change limit. All proposals still require finalization.
Delegators participate indirectly through the validator pools they support. Their delegated stake contributes to the pool owner's DAO voting weight.
Review validator votes on each proposal's page, or use the Validator Candidate Participation Table on the validator page to review a pool owner's votes and participation. Consider that record, together with the owner's stated positions, when choosing a pool whose governance decisions align with your preferences.

- Executive Summary
- Background
- Network Features and Participation
- Technical Architecture
- Coin Economy
- DAO Governance
- Diamond UI
- Network Security System
- DMD Naming System
- DMD Chatrooms
- Roadmap
- Community Representatives