Governance & Permissions
Lucid provides configurable governance and permission infrastructure for managing proposals, voting systems, operational approvals, veto coordination, and cross-chain governance execution.
Governance infrastructure is modular and can be configured independently depending on the organisation’s operational requirements.
Supported governance systems include:
- 1 Token 1 Vote
- Quadratic Voting
- multisignature governance
- veto infrastructure
- cross-chain governance coordination
- governance timelocks
- proposal threshold systems
Governance Infrastructure
Governance infrastructure coordinates:
- proposal creation
- voting execution
- veto operations
- proposal approval
- execution delays
- governance permissions
- cross-chain governance coordination
Governance modules are deployed independently during organisation setup and can operate across multiple supported chains depending on configuration.
Supported Governance Modules
Lucid supports multiple governance modules that can be combined modularly inside the same organisation.
| Module | Purpose |
|---|---|
| 1 Token 1 Vote | Standard token-weighted governance |
| Quadratic Voting | Reduced influence concentration through quadratic weighting |
| Pre-Vote Veto | Proposal veto before voting begins |
| Pre-Execution Veto | Proposal veto before execution |
| Multi-Bridge Veto | Cross-chain governance veto coordination |
Governance modules can operate independently or together depending on the selected governance architecture.
1 Token 1 Vote
1 Token 1 Vote is a standard governance model where:
- each governance token represents one vote
- voting power scales linearly with token ownership
- governance outcomes are determined by total voting weight
This model is designed for:
- straightforward governance coordination
- token-weighted proposal execution
- traditional DAO governance structures
Quadratic Voting
Quadratic Voting is designed to reduce governance dominance by large token holders.
Under this model:
- additional voting power becomes progressively more expensive
- voting influence scales quadratically rather than linearly
- governance outcomes reflect preference intensity more evenly
Example:
- 1 vote costs 1 unit
- 2 votes cost 4 units
- 3 votes cost 9 units
This structure:
- reduces governance concentration
- improves collective decision balancing
- introduces more distributed governance participation
Quadratic Voting can also operate as part of hybrid governance systems through configurable thresholds.
Quadratic Thresholds
Lucid supports hybrid governance through configurable quadratic thresholds.
Under this model:
- voting remains linear up to a specified percentage
- quadratic weighting activates beyond the configured threshold
Example:
- first 5% of voting power uses 1 Token 1 Vote
- voting power above 5% uses Quadratic Voting
This structure balances:
- governance accessibility
- whale resistance
- operational simplicity
- voting fairness
Gitcoin Passport Integration
Quadratic Voting optionally supports Gitcoin Passport integration.
Gitcoin Passport provides:
- sybil resistance
- identity verification
- reputation coordination
- governance integrity improvements
This helps reduce governance manipulation while maintaining user privacy.
Gitcoin Passport support is available only for Quadratic Voting systems.
Quorum Threshold
The quorum threshold defines the minimum percentage of total voting power required for a proposal to become valid.
If quorum is not reached:
- proposals remain invalid
- execution cannot occur
- governance actions fail regardless of vote outcome
Quorum thresholds help ensure:
- sufficient governance participation
- representative proposal outcomes
- operational governance integrity
Proposal Threshold
The proposal threshold defines the minimum voting power required for proposal submission.
This prevents:
- governance spam
- low-quality proposals
- insufficiently supported governance actions
Proposal thresholds can be configured depending on organisational governance requirements.
Voting Timing Configuration
Governance systems support configurable timing infrastructure for proposal coordination.
Supported timing parameters include:
| Parameter | Purpose |
|---|---|
| Voting Period | Duration proposals remain open for voting |
| Vote Delay | Delay before voting becomes active |
| Pre-Execution Timelock | Delay before approved proposals execute |
These timing systems coordinate:
- governance review windows
- veto periods
- operational execution delays
Pre-Vote Veto
Pre-Vote Veto allows governance proposals to be vetoed before voting begins.
This infrastructure:
- operates during the configured vote delay period
- introduces additional governance oversight
- prevents proposals from entering active voting
The vote delay duration determines how long proposals remain eligible for veto before voting activation.
Pre-Execution Veto
Pre-Execution Veto allows proposals to be vetoed after voting succeeds but before execution finalises.
This infrastructure:
- operates during the execution timelock period
- provides additional operational oversight
- prevents approved proposals from executing immediately
The pre-execution timelock determines the veto window duration.
Multi-Bridge Governance Coordination
Governance infrastructure can coordinate proposal execution across multiple supported chains through Multi-Bridge infrastructure.
Cross-chain governance infrastructure supports:
- multi-chain proposal coordination
- interoperability-aware governance execution
- cross-chain veto coordination
- distributed governance infrastructure
Additional operational execution flows are covered in the Multi-Hop & Multi-Consensus section.
Multisignature Governance
Governance infrastructure supports multisignature operational coordination.
Multisignature systems can manage:
- governance approvals
- veto operations
- protocol upgrades
- operational execution
- cross-chain governance actions
Supported multisignature thresholds can include:
- 2-of-3
- 3-of-5
Thresholds determine how many authorised signers are required before execution finalises.
Governor Deployment
Governors are deployed during organisation configuration.
Current governance deployment infrastructure:
- supports up to 10 governors per organisation
- supports configurable governance models
- supports configurable governance thresholds
- supports multi-chain voting coordination
Some governance integrations may currently require governors to deploy on a single chain depending on interoperability support.
Governance Permissions
Governance permissions determine:
- who can submit proposals
- who can vote
- who can veto proposals
- who can execute governance actions
- who can approve operational upgrades
Permission visibility and execution access depend on:
- governance configuration
- multisignature ownership
- operational role assignments
Governance permissions are configured during organisation deployment and can later be updated through operational upgrade infrastructure.

