Governance

Cardano on-chain governance (CIP-1694): governance actions and their votes, DReps, the constitutional committee and the treasury.

DRepsStake pools
Treasury
₳1.37B
Reserves
₳6.08B
DReps
1,049
312 active
Delegated to DReps
₳5.25B
74.1% of stake has a voting choice
Always abstain
₳10.38B
198,192 delegators
No confidence
₳136.10M
6,381 delegators
Governance actions
158
3 live · 81 enacted
Committee
7 members
quorum 2/3

Live governance actionsepoch 660

Infoexpires after epoch 663 · 3 epochs left
Should stakePoolTargetNum (k) be raised from 500 to 1000? (SPO poll)

This Info Action asks the Cardano community, and in particular Stake Pool Operators (SPOs), whether there is sufficient SPO support to proceed with a later Parameter Change Governance Action that would raise **`stakePoolTargetNum` (`k`)** from 500 to 1000. It follows the 2023 SPO poll but considers `stakePoolTargetNum` on its own. To determine whether sufficient SPO support exists, votes shall be tallied according to the standard CIP-1694 voting semantics; this proposal introduces no alternative turnout-based formula. SPO voting power is stake-weighted. An explicit ABSTAIN vote is excluded from active voting stake, while registered stake that does not vote behaves like a NO vote. Sufficient support is established only if explicit SPO YES votes represent more than 50% of the applicable active SPO voting stake. This majority-by-stake standard follows the existing Cardano governance model for actions requiring SPO approval. The Cardano Constitution requires more than 50% support by active block-production stake where SPO approval is required for security-critical parameter changes. DReps are invited to vote and submit rationales, but DRep votes are not included when determining whether this Info Action has established an SPO mandate. Because this is an Info Action, the >50% standard is a declared interpretation of the poll result, not an on-chain ratification threshold for Info Actions themselves. CIP-1694 assigns Info Actions a 100% formal threshold so they remain polling mechanisms rather than enactable governance actions. If more than 50% SPO support is reached under the normal CIP-1694 calculation, this Info Action establishes a clear SPO mandate to proceed with a separate Parameter Change Governance Action raising `stakePoolTargetNum` from 500 to 1000. If the threshold is not reached, this Info Action has not established majority SPO support for `k=1000`. The result must not be interpreted as a mandate for any alternative increase in `stakePoolTargetNum`; a different value would require its own explicit SPO approval under the same CIP-1694 voting semantics. Because SPOs were already polled on increasing `k` in 2023, substantially similar proposals should not be repeatedly resubmitted absent materially changed economic, technical, or network conditions.

DReps3.8%
Pools0.7%
Committee16.7%
Parameter changeexpires after epoch 661 · 1 epoch left
Reduce minPoolCost to 75 ada

This governance action proposes reducing `minPoolCost` from 170,000,000 Lovelace (170 ada) to 75,000,000 Lovelace (75 ada), a decrease of approximately 55.9%. No other protocol parameters are changed by this action.

DReps33.6% / 67%
Pools0.0%
Committee42.9% / 67%
Treasury withdrawal₳11.79Mexpires after epoch 661 · 1 epoch left
Withdraw 11,787,063 ada for the OpenZeppelin Stack administered by Intersect

This treasury withdrawal proposal requests funding for the design, implementation, security audit, and ecosystem adoption of a comprehensive open-source development stack for Cardano, delivered over an initial 12 months in quarterly milestones. The proposal bundles three tightly coupled workstreams into a single integrated engagement, led by the Reference Implementations and built around them: * OpenZeppelin Reference Implementations for Cardano: three production-ready, end-to-end blueprints targeting strategic DeFi and institutional use cases: a Cardano Liquid Staking Protocol, a Self-Repaying Loans Protocol, and a Tokenized Money Market Fund. * OpenZeppelin Contracts Library for Cardano: a secure, audited, standardized contracts library tailored for Cardano's eUTXO model and Plutus environment, including Contracts Wizard integration, AI development tools, and documentation. * Security Retainer: dedicated security capacity covering line-by-line audits of the library and full-stack security reviews and penetration testing of every Reference Implementation. OpenZeppelin also commits to a Developer Enablement and Co-Marketing program, included at no additional cost, to drive ecosystem and institutional adoption of the libraries and Reference Implementations. This proposal requests a total treasury withdrawal of 11,787,063 ada. The full budget breakdown and disbursement mechanics are set out in the Rationale.

DReps3.8% / 67%
Pools0.0%
Committee42.9% / 67%
Treasury & reserves by epochlast 73 epochs (~1 year): −₳230.88M
All governance actions
Constitutional committeequorum 2/3
Member (cold credential)StatusTerm endsVotes (yes / no / abstain)
cc_cold1zd7rfcpypw…dq9jkwn2scriptauthorizedepoch 7994 / 0 / 0
cc_cold1zg90nyz8hj…cgjkqykpauthorizedepoch 799—
cc_cold1zvt0am7zyh…ssazjmn9scriptauthorizedepoch 799—
cc_cold1zvvcpkl344…qqeatx67scriptauthorizedepoch 726—
cc_cold1zwz2a08a8c…6s4m87ehscriptauthorizedepoch 726—
cc_cold1zwt49epsde…3g5xu74hscriptauthorizedepoch 726—
cc_cold1zgf5jdusmx…4q68as9wauthorizedepoch 799—
Rules in force
Action deposit
₳100K
Action lifetime
6 epochs
DRep deposit
₳500
DRep activity window
20 epochs
Committee min size
7
Committee max term
146 epochs
Approval thresholdYes share needed
DReps · motion of no confidence67%
DReps · committee update67%
DReps · committee update (no-confidence state)60%
DReps · new constitution75%
DReps · hard fork60%
DReps · parameters (network)67%
DReps · parameters (economic)67%
DReps · parameters (technical)67%
DReps · parameters (governance)75%
DReps · treasury withdrawal67%
Pools · motion of no confidence51%
Pools · committee update51%
Pools · committee update (no-confidence state)51%
Pools · hard fork51%
Pools · security parameters51%
Source: Koios (public)updated 2h agoThresholds are read from the own node’s protocol parameters; votes and tallies from Koios.