Skip to main content

Scope note

This page is the public lookup surface for DerivaDEX governance mechanics. It covers proposal parameters, token-count thresholds, proposal and voting constraints, queue and execute timing, and governance event families. It does not publish private review workflow or environment-specific governance operations runbooks.

Current repo-backed governance parameters

ParameterCurrent valueUnitPublic meaning
proposalMaxOperations10actionsmaximum actions carried by one proposal
votingDelay1blockdelay between proposal creation and voting start
votingPeriod17280blocksstandard voting window
gracePeriod1209600secondstime a successful proposal can remain queued before expiring
timelockDelay259200secondsstandard queue-to-execute delay
quorumVotes4percent-style governance parameterminimum support threshold used to derive quorum vote count
proposalThreshold1percent-style governance parameterminimum proposer threshold used to derive required proposing power
skipRemainingVotingThreshold50percent-style governance parameterthreshold that can end the practical wait for the remaining voting period when for or against votes exceed it

Derived vote-count thresholds asserted in repo tests

Read surfaceAsserted countMeaning
getQuorumVoteCount()2,000,000 DDXminimum support count needed for standard success at voting close
getProposerThresholdCount()500,000 DDXminimum voting power required to create a proposal
getSkipRemainingVotingThresholdCount()25,000,000 DDXfor- or against-vote count that can satisfy the skip-remaining-voting condition
getMaximumVotingCapCount()24.9% of total supplymaximum effective vote weight one participant can wield through the Dip12 voting-cap path

Proposal creation constraints

ConstraintPublic contract
proposer thresholdproposer must be above the current proposer-threshold count
action paritytargets, values, signatures, and calldatas must stay length-matched
empty proposalproposal with zero actions reverts
action countproposal with more than 10 actions reverts
live-proposal ruleone proposer cannot keep more than one live proposal at a time

Voting mechanics

TopicPublic contract
voting startvotes cannot be cast before the voting-delay window opens
voting power requirementa voter with zero voting power cannot cast a vote
duplicate votingvoter cannot cast a second vote on the same proposal
signed votingcastVoteBySig is supported for offline-signature vote submission
vote receiptsgetReceipt(proposalId, voter) is the public read surface for hasVoted, support, and counted vote weight
historic vote inspectionDDX vote accounting supports reads such as getCurrentVotes and getPriorVotes for governance-weight inspection
delegation pathDDX delegation changes governance weight through delegate and delegateBySig flows

Success, queue, and execute rules

StagePublic contract
success conditionproposal can succeed either by crossing the skip-remaining-voting threshold or by ending with majority support plus quorum
queue eligibilityonly a succeeded proposal can be queued
execute eligibilityonly a queued proposal can be executed
standard execute delayqueued proposal must remain queued through the timelock delay before execution
expiry boundaryqueued proposal must execute before the grace-period window expires
fast-path actionscertain pause-sensitive actions can carry a shorter queue delay than the standard timelock path

Governance safety constraints

ConstraintPublic contract
minimum skip thresholdskipRemainingVotingThreshold cannot initialize below 50
quorum relationshipquorumVotes cannot be greater than or equal to skipRemainingVotingThreshold
invalid governed updatesgoverned attempts to set invalid quorum or skip-threshold values revert at execution

Governance event families

EventWhy it matters
ProposalCreatedproves the proposal ID, proposer, action set, and voting window
VoteCastproves voter, support direction, and counted vote weight
ProposalQueuedproves the proposal entered queue and records ETA
ProposalExecutedproves proposal execution completed
ProposalCanceledproves proposal cancellation occurred
QueueTransactionproves one proposal action was queued
ExecuteTransactionproves one proposal action executed
CancelTransactionproves one queued proposal action was canceled

Boundary note

This page describes public mechanics and thresholds, not governance strategy or private operational review. Use the process reference for surface routing, and use current on-chain reads plus current deployment context when exact live governance state matters.
Last modified on April 12, 2026