Three-line summary:

1. Cardano Constitution v2.4 removes non-binding expectations, the Budget Info Action mechanism, and mandatory CC conduct rules, streamlining governance.
2. It adds clear definitions, enforces immutability of proposal documents, and applies treasury audit/accountability safeguards to all withdrawals.
3. This version also incorporates feedback from EMURGO.

Three helpful links

1. CARDANO BLOCKCHAIN ECOSYSTEM CONSTITUTION v2.4
   https://ipfs.io/ipfs/bafkreih62pydt57supou6dn5lqbf5klr7xu4xi2rrs7tl3thaufiqmvo24

2. List of changes from v1.0 to v2.4.pdf
   https://ipfs.io/ipfs/bafybeihsv7crutk4xrwut5p5fdvgeum45hioazn2dldnqk2ljiv7sp3oda

3. List of changes from v2.3 to v2.4.pdf
   https://ipfs.io/ipfs/bafybeibu2v7l6z3k5jhhdtzv74fcrlaedxwdwtxu2ogwudykyfjjfreppu

The proposed changes aim to:

1. Simplify governance by removing non-binding expectations and redundant mechanisms like Budget Info Action.
2. Improve clarity and consistency through unified terminology, added definitions, and streamlined provisions.
3. Strengthen accountability by applying treasury audit safeguards universally and ensuring proposal documents remain immutable.

Please see the Rationale section for details.

I. Summary of Changes and Rationale (v1.0 → v2.4)

1. Items Removed from the 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, 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. Summary of Changes and Rationale (v2.3 → v2.4)

EMURGO expressed concerns regarding three specific wording changes introduced in Constitution v2.3 and voted NO on its adoption.
Since EMURGO is the largest DRep, and changing the Constitution without its consent would be highly impractical, these three modifications are reverted to the wording used in the original Constitution (v1.0).

1. Change Ada Holder to ada owner and remove this definition.

2. Revert the wording of provisions related to custodians to the form used in v1.0.

3. Revert the wording of provisions related to independent audits to the form used in v1.0.