CARDANO BLOCKCHAIN ECOSYSTEM CONSTITUTION v2.3
On-chain changes
- New constitutionipfs://bafkreibyaftvpujgjernbcj2rgrwg3fntsg37cxx5bdgpy4hyt4eki5r2e
- Guardrails scriptfa24fb305126805cf2164c161d852a0e7330cf988f1fe558cf7d4a64
Abstract
Three-line summary:
- Cardano Constitution v2.3 removes non-binding expectations, the Budget Info Action mechanism, and mandatory CC conduct rules, streamlining governance.
- It adds clear definitions, enforces immutability of proposal documents, and applies treasury audit/accountability safeguards to all withdrawals.
- Community review of v2.0 had 86.23% DRep participation, and v2.3 incorporates feedback and improvements, addressing prior concerns to reinforce legitimacy and broad input.
Three helpful links
CARDANO BLOCKCHAIN ECOSYSTEM CONSTITUTION v2.3
https://ipfs.io/ipfs/bafkreihjgclyeemuvvn27mil5whoexjsuhn3fuwgjefawwbonmwo6hsxsqList of changes from v1.0 to v2.3.pdf
https://ipfs.io/ipfs/ipfs/bafybeigshlsvztihfem32ei2n7ijucbmiqzr5ulxoyezvckvzisqiee3faList of changes from v2.0 to v2.3.pdf
https://ipfs.io/ipfs/bafybeihjegoita5u67sr6q2cplb33zglytwdo7355u6f2wn4wayhq6uy4e
Motivation & rationale
The proposed changes aim to:
- Simplify governance by removing non-binding expectations and redundant mechanisms like Budget Info Action.
- Improve clarity and consistency through unified terminology, added definitions, and streamlined provisions.
- Strengthen accountability by applying treasury audit safeguards universally and ensuring proposal documents remain immutable.
Please see the "Rationale" section for details.
I.Simple summary of the changes and their rationale from Cardano Constitution v1.0 to v2.3
1. Items Removed from Constitution v1.0
(a) Expectations and Encouragement clauses
Expectations: ARTICLE III. Section 6 (off-chain governance management), ARTICLE V. Section 3 (DRep code of conduct), ARTICLE V. Section 4 (DRep selection tool), ARTICLE VII. Section 1 (CC expertise), ARTICLE VII. Section 7 (CC tool support)
Encouragement: ARTICLE VI. Section 3 (SPO code of conduct), ARTICLE VIII. Section 1 (constitutional discussion)
Rationale: These provisions were aspirational or advisory in nature (expectations/encouragements), not enforceable constitutional rules.
(b) Budget Info Action Provisions (ARTICLE III. Section 4, ARTICLE IV, ARTICLE VII. Section 4)
Rationale: The Budget Info Action mechanism was removed to simplify governance. Its requirements have been absorbed into Treasury Withdrawal Governance Actions.
(c) Obligation to Create a CC Code of Conduct (ARTICLE VII. Section 6)
Rationale: This was considered an operational detail better left to community practice rather than a constitutional mandate. The CC may still adopt codes of conduct, but it is no longer a constitutional requirement.
2. Changes and additions (excluding deletions)
(a) Overall - Fixed typos, simplified wording, and unified terminology.
Rationale: Improves readability and ensures consistency
(b) Defined Terms: - Added definitions such as Active Voting Stake, Ada Holders, DRep, SPO, Net Change Limit, Treasury Withdrawal Recipient.
Rationale: Eliminates ambiguity and ensures consistency in interpretation
(c) ARTICLE II, Section 6 – Introduced requirement that “The document hosted by such a URL shall be immutable.”
Rationale: ensure proposals cannot be altered after submission, protecting integrity and trust
(d) ARTICLE II Section 7 :Reassigned conditions previously tied to the Budget Info Action, making them mandatory at the time of Treasury Withdrawals after its removal
Rationale: strengthen accountability and transparency in the use of Treasury funds and preserve oversight and audit safeguards after removing the Budget Info Action mechanism
II.Simple summary of changes and reasons from Cardano Constitution v2.0 to v2.3
1. Editorial & Structural Improvements
- Terminology: Standardized terms like “Cardano Community Member”, “Ada Holders”.
- Definitions: Definitions: Clarified the “Net Change Limit” (maximum treasury withdrawal per period) and refined the definition of “Stake Pool Operator” (the entity controlling cold keys).
2. Section-Specific Revisions
- ARTICLE II Section 1: Clarifies no formal membership is needed to use or benefit from Cardano.
- ARTICLE II Section 5: Simplifies redundant provisions regarding SPOs.
- ARTICLE II Section 6: Simplification of wording in some provisions.
- ARTICLE II Section 7: (1) Removed: The requirement to include the “location and identity of the recipient” in withdrawal terms, the explicit requirement to budget for audit costs, and the explicit statement that “withdrawals shall be used for the purpose set out in paragraph 1” (2) Changed: The special requirements that previously applied only to withdrawals exceeding 1,000,000 ADA in a two-year period (i.e., appointing independent auditors and publishing annual reports, designating administrators to oversee funds, and keeping funds in auditable separate accounts delegated to abstain) now apply as general requirements for all withdrawals.
- TREASURY-04a (x): Deletes requirement for treasury withdrawal roadmaps to be approved via Info Action.
III.Evidence of widespread community reviews:
Constitution v2.0 received review and voting by 86.23% of total DRep voting power, including both Yes/No/Abstain votes.
Many DReps submitted detailed analyses publicly.
v2.3 builds on v2.0 with rational improvements and direct incorporation of on-chain feedback.
Concerns regarding insufficient discussion of the constitution have been reasonably addressed in v2.3.
Rationale highlights
Why some of the largest DReps voted for and against, in their own words.
Summary Yoroi DRep votes NO on the governance action to adopt Cardano Constitution v2.3. Rationale Yoroi would like to sincerely thank Yuta for the time, care, and consistency he’s shown in leading the continued evolution of the Cardano Constitution. The...
Summary
Yoroi DRep votes NO on the governance action to adopt Cardano Constitution v2.3.
Rationale
Yoroi would like to sincerely thank Yuta for the time, care, and consistency he’s shown in leading the continued evolution of the Cardano Constitution. The community benefits greatly from these ongoing discussions and refinements, and we recognize how much thoughtful work went into v2.3.
That said, after careful review, we believe several revisions in this version could unintentionally reduce clarity or weaken existing safeguards that protect Cardano’s decentralized decision-making process.
Audit Requirement:
The new phrasing around audits (“appoint independent auditors”) creates practical uncertainty over who is responsible for selection, funding, and timing. The previous version already offered a clear and effective standard through Intersect’s audit process, which ensured accountability without procedural confusion.
Custodian Consent:
Expanding the clause to let custodians “vote or delegate” on behalf of ADA holders, combined with the term shift from “owners” to “holders,” introduces potential ambiguity over user consent and could concentrate voting power among large custodial entities.
Each of these points could likely be addressed through clarification and community alignment, but together they present enough risk to justify a cautious NO vote at this stage.Conclusion
Yoroi deeply appreciates Yuta’s continuous effort to make Cardano’s Constitution more complete and approachable. This No vote is not a rejection of that work, it’s a call for more dialogue before codifying these specific changes. We’re very happy to work together and help facilitate open discussion toward a future version that strengthens both clarity and decentralization in Cardano’s governance.
My reasons for voting YES on "CARDANO BLOCKCHAIN ECOSYSTEM CONSTITUTION v2.3" are well summarized in the "Three-line summary" description in the governance action metadata: Cardano Constitution v2.3 removes non-binding expectations, the Budget Info Action...
My reasons for voting YES on "CARDANO BLOCKCHAIN ECOSYSTEM CONSTITUTION v2.3" are well summarized in the "Three-line summary" description in the governance action metadata:
- Cardano Constitution v2.3 removes non-binding expectations, the Budget Info Action mechanism, and mandatory CC conduct rules, streamlining governance.
- It adds clear definitions, enforces immutability of proposal documents, and applies treasury audit/accountability safeguards to all withdrawals.
- Community review of v2.0 had 86.23% DRep participation, and v2.3 incorporates feedback and improvements, addressing prior concerns to reinforce legitimacy and broad input.
However, I will be regularly reviewing community rationales voting NO and listening carefully to any opposing arguments.
私が、「CARDANO BLOCKCHAIN ECOSYSTEM CONSTITUTION v2.3」にYESを投票する理由は、ガバナンスアクションのメタデータの「Three-line summary」の記述によく要約されています。
- Cardano Constitution v2.3 では、拘束力のない期待、予算情報アクション メカニズム、および必須の CC 行動ルールが削除され、ガバナンスが合理化されます。
- 明確な定義を追加し、提案文書の不変性を強化し、すべての引き出しに財務監査/説明責任の保護措置を適用します。
- v2.0 のコミュニティレビューでは DRep の参加率が 86.23% で、v2.3 ではフィードバックと改善が組み込まれ、以前の懸念に対処して正当性と幅広い入力が強化されています。
ただ、私はNOを投票するコミュニティのRationalを定期的に確認して、反対意見をよく聞く予定です。
Summary EMURGO as DRep votes NO on the governance action to adopt Cardano Constitution v2.3. Rationale EMURGO deeply appreciates Yuta’s leadership and continued dedication in advancing the Cardano Constitution. The proposed v2.3 introduces valuable...
Summary
EMURGO as DRep votes NO on the governance action to adopt Cardano Constitution v2.3.
Rationale
EMURGO deeply appreciates Yuta’s leadership and continued dedication in advancing the Cardano Constitution. The proposed v2.3 introduces valuable refinements to structure, consistency, and readability that contribute to the ongoing evolution of Cardano’s governance framework.
However, several changes in this version raise substantive concerns regarding governance clarity and decentralization safeguards. The revised Net Change Limit weakens the explicit link between approved budgets and treasury withdrawals, potentially diluting fiscal accountability.
The updated Audit Requirement creates uncertainty around execution and funding responsibility, reducing procedural clarity. Additionally, the expanded Custodian Consent clause broadens custodial authority, which may inadvertently increase centralization risks and weaken user consent protections.
While these issues may stem from good intentions to streamline the Constitution and the governance process, the current wording introduces ambiguity in areas that are foundational to Cardano’s accountability and decentralized governance model.
Conclusion
EMURGO’s NO vote reflects a commitment to preserving procedural integrity, transparency, and decentralization within Cardano’s constitutional design. We commend Yuta’s continued effort and emphasize that EMURGO remains ready to collaborate and facilitate further discussions to refine these sections in future amendments, ensuring clarity and balance in the governance framework moving forward.
TL;DR: EDC voted YES on gov_action1ezp0r9rgf4njx93p9uq7l3kjs9m739jm0ntf26vplcmucec4jc0qqxjlfrc; Thanks Yuta for putting in the work to update the Constitution. The update brings clarity on definitions (now being part of the document body), removed budget...
TL;DR: EDC voted YES on gov_action1ezp0r9rgf4njx93p9uq7l3kjs9m739jm0ntf26vplcmucec4jc0qqxjlfrc;
Thanks Yuta for putting in the work to update the Constitution. The update brings clarity on definitions (now being part of the document body), removed budget info actions, reducing the amounts of votes DReps have to do (though in reality only a on-chain proposal brings attention to a topic ecosystem wide and proposals will pop up multiple times with refinements and feedback from previous votes.)