Skip to main content

User and proposal flows

User flow​

Users begin by exploring the Governance Tool, which provides essential information about the governance system and its processes.

Registration​

Users register using a MetaMask wallet, which automatically creates:

  • A citizen account
  • An FT4 account

Rank advancement​

Users can progress within the governance system through active participation:

  • Citizens may be promoted to counselors based on an admin decision or through a successful governance proposal.

Ban (upcoming feature)​

A ban list will enable admins to remove non-compliant users from the governance system.

Cooldown periods​

To prevent spam and ensure fair governance, cooldown mechanisms will regulate actions:

  • Proposal creation cooldown: Limits how often users can submit proposals.
    • Default setting: Disabled in the demo environment.
    • Admins and counselors can enable and configure cooldowns.
  • Veto execution cooldown: Restricts the frequency with which veto actions can be performed.

Proposal flow​

Creating a proposal​

Citizens can draft proposals by providing the following information:

  • Title
  • Category
  • Description
  • Duration
  • Voting options and commands

Validation​

  • The system automatically validates proposals upon saving.
  • It checks for compliance with predefined rules, such as character limits and content flags.
  • Validation logic is configurable.

Approval​

  • Proposals require admin or counselor approval through a voting process.
  • Demo setting: Admins must manually save a draft before clicking approve.

Verification​

  • The system verifies if a proposal meets quorum requirements.
  • Verification occurs after each approve or disapprove vote.
  • Demo rule: At least 50 percent of counselors must approve a proposal for it to be verified.

Voting​

Citizens vote based on:

  • Token balance or stake
  • Voting power strategies, such as linear, quadratic, or hybrid models

The voting period ends when:

  • The set time limit expires.
  • A predefined threshold is met.
  • Demo feature: Admins can manually end voting.

Veto​

  • Admins and counselors can veto proposals within a defined period.
  • The veto process is separate from regular voting:
    • Veto decisions go through an approval or disapproval phase, requiring additional review before finalization.
    • When a veto is initiated, the proposal moves into a special "ON_VETO" state, suspending the normal decision-making process.
    • Vetoing requires additional checks, making it a privileged action restricted to specific roles (admins and counselors).
    • Vetoing acts as a blocking mechanism, preventing a proposal or option from proceeding unless the veto is overturned.

Execution​

  • The system executes commands from the winning proposal.
  • After execution, participants receive a refund of their voting power.