IO & VacuumLabs: Enhancing Plutus - Performance, Correctness, and Usability
7 of 7 committee members voted
- Ace Alliance71aa5b3a…8f04YesActive · term ends epoch 726Rationale
Ace Alliance finds the proposed "IO & VacuumLabs: Enhancing Plutus - Performance, Correctness, and Usability" Treasury Withdrawals Governance Action constitutional. Rationales are archived at https://github.com/ace-alliance/ace-voting/
A PDF version of this rationale is also made available.
"IO & VacuumLabs: Enhancing Plutus - Performance, Correctness, and Usability" (gov_action1w0s...czhx6t) is a Treasury Withdrawals Governance Action and is therefore governed by both the general proposal standards in Article II, Section 6 and the additional Treasury Withdrawal standards in Article II, Section 7 of the Cardano Constitution.
This TWGA seeks to withdraw ₳11,877,575 from the Cardano Treasury to fund three connected workstreams strengthening the Plutus smart contract platform: an expansion of UPLC capabilities and primitives, including casing on the built-in Data type, additional BuiltinValue functions, the multiIndexArray builtin, an investigation of the redundant scope check, and a SNARK-friendly hash CIP with C bindings conditional on benchmarks; a formal-specification, conformance, and security workstream, including a property-based conformance testing framework, an Agda formalization of programmatic built-ins, and a systematic security audit of the evaluator and costing code; and a developer-experience workstream improving the compiler architecture, error reporting, and project setup. Delivery runs from Q3 2026 through Q2 2027, with the work delivered as a co-venture between Input Output and VacuumLabs. Funds are directed into Intersect's 2025 Treasury Reserve Smart Contract (stake17xzc8pt7fgf0lc0x7eq6z7z6puhsxmzktna7dluahrj6g6ghh5qjr), administered by Intersect on behalf of Cardano Development Holdings.
The procedural standards of Article II.6 are satisfied: the proposal anchors to an IPFS-hosted document with the on-chain blake2b-256 hash, a content-addressed form "immutable and incapable of being altered after submission," and the metadata provides the title, abstract, justification, and supporting materials required by II.6.2.
The substantive Article II.7 requirements are met as well. Under Article II.7.1, "Treasury Withdrawals actions must specify the terms of the withdrawal," and the proposal specifies the purpose (three named workstreams), period (Q3 2026 through Q2 2027 with milestone-level dates), itemized costs (across development, infrastructure, security and audits, legal and compliance, ecosystem engagement, operations and delivery, governance, and other line items), and refund circumstances (end-of-period sweep and proportional return on cancelled or reduced deliverables). The disclosure requirement of Article II.7.2 is met by a Prior Treasury Receipts section stating aggregate prior allocations of ₳130,708,860 and prior withdrawals of ₳78,459,777 across IO and affiliated entities. The 350M Net Change Limit covering Epoch 613 to Epoch 713 is set, and this ₳11,877,575 ask does not exceed it, satisfying Article II.7.3 and Appendix I guardrail TREASURY-02a.
A 3rd Party Assurer funded as part of the withdrawal supports milestone acceptance, satisfying the periodic independent audit and oversight allocation under Article II.7.4. Article II.7.5 is satisfied by Intersect's designation as Administrator, acting on behalf of Cardano Development Holdings, operating through the TRSC and PSSC framework with milestone-based disbursement controls and a five-member external Oversight Committee (Sundae Labs, Cardano Foundation, Dquadrant, Xerberus, NMKR). The custody requirement of Article II.7.6 is satisfied by the proposal's commitment that the TRSC stake account uses auto-abstain DRep delegation, with PSSC creation on Legal Contract readiness, milestones recorded in metadata, and a community-audit dashboard, on the same Intersect TRSC pattern we have accepted as constitutional in prior actions in this family.
For these reasons, Ace Alliance finds the proposed "IO & VacuumLabs: Enhancing Plutus - Performance, Correctness, and Usability" Treasury Withdrawals Governance Action constitutional under Article II.6.1 and Article II.7.1 through II.7.6.
- Cardano Curia84feba94…6bd5YesActive · term ends epoch 799Rationale
Cardano Curia finds this Treasury Withdrawal constitutional under the Cardano Constitution (v2.4), because (as finalized) it is properly specified and includes immutable canonical documentation plus the required administration/oversight, auditability, and custody controls for a Treasury Withdrawal.
What is being proposed
This governance action proposes a Treasury Withdrawal from the Cardano Treasury to fund the scope described in the action’s canonical proposal linked from GovTool.
Constitutional and guardrails consistency (v2.4)
A Treasury Withdrawal is constitutional when it meets (a) the governance action standards for a stable, legible, immutable off-chain reference (URL + hash / content-addressed reference), and (b) the Treasury Withdrawals standards requiring: clear purpose and delivery period; relevant costs/expenses; refund/return circumstances; disclosure of prior treasury receipts (last 24 months); Net Change Limit compliance; allocation for independent audits and oversight metrics; designation of one or more administrators responsible for monitoring funds and verifying deliverables; and segregated auditable holding accounts (delegated to predefined abstain) for any funds held by administrators prior to onward disbursement.
Basis for a YES finding (positive)
Cardano Curia supports constitutionality because the finalized submission state:
- Locks the canonical proposal to an immutable reference with a verifiable content hash (reducing bait-and-switch risk).
- Specifies purpose, delivery period, and cost/expense framing sufficient for responsible treasury stewardship.
- Designates administrators / responsible parties and includes oversight metrics and reporting expectations.
- Includes independent audit provisions and budget allocation for audit/oversight.
- Implements custody controls consistent with the Constitution (segregated, auditable holding arrangements for administrator-held funds, delegated to predefined abstain until disbursement).
Determination
For the reasons above, Cardano Curia determines this Treasury Withdrawal is constitutional under Constitution v2.4, provided the on-chain references exactly match the immutable canonical documents (content/hash match).
Cardano Curia votes YES on constitutionality (5–0). The action is constitutional under Constitution v2.4 given immutable documentation and explicit administration/auditability/custody controls consistent with Treasury Withdrawal standards.
- Cardano Japan Council725d4d44…7b31YesExpired · term ends epoch 653Rationale
We consider this governance action to be constitutional.
This proposal is a Treasury Withdrawal Governance Action to withdraw ₳11,877,575 from the Cardano Treasury for the project “Enhancing Plutus - Performance, Correctness, and Usability” by Input Output and VacuumLabs. Regarding Article 2, Section 6, Paragraphs 1 and 2 of the Cardano Constitution, this proposal adopts an immutable off-chain reference using IPFS. Furthermore, the proposal text includes the title, summary, motivation, rationale, deliverables, roadmap, budget, risks, and oversight structure, and we determine that it presents information sufficient for evaluation as a Governance Action. Regarding Article 2, Section 7, Paragraphs 1 and 2, in addition to the purpose of the Treasury Withdrawal, implementation period, cost breakdown, and repayment conditions, past Treasury receipt records are disclosed under the “Prior Treasury Receipts” section. Regarding Article 2, Section 7, Paragraph 3, the requested amount for this proposal is ₳11,877,575, which falls within the 350M ADA Net Change Limit applicable to Epochs 613-713 at the time of submission. Furthermore, the requested amount is stated in ADA, and the USD equivalent is provided for reference only. Article 2, Section 7, Paragraphs 4 and 5 describe the audit and oversight framework, including third-party guarantees, the Oversight Committee, audits, reporting obligations, and dashboards, and designate Intersect as the administrator. Furthermore, Article 2, Section 7, Paragraph 6 describes the use of Treasury Reserve Smart Contract (TRSC) and Project-Specific Smart Contracts (PSSC) for segregated management, a structure designed for on-chain auditability, non-delegation to SPOs, and delegation to auto-abstain DReps. We determine that this structure is intended to align with the requirements of “auditable by the Cardano Community,” “separate accounts,” “not delegated to a SPO,” and “delegated to a predefined abstain voting option.” Therefore, as no clear conflict with the Cardano Constitution has been identified, we determine that this proposal is constitutional.
For the reasons stated above, we determine that it is constitutional.
- Eastern Cardano Council2ea7a78e…10ecYesActive · term ends epoch 726Rationale
We have determined that this treasury withdrawal governance action is constitutional.
The governance action with ID "gov_action1w0s...czhx6t" and title "IO & VacuumLabs: Enhancing Plutus - Performance, Correctness, and Usability" is a Treasury Withdrawal, and is therefore subject to the following sections and guardrails in the Cardano Constitution.
ARTICLE II, Section 6 of the Cardano Constitution states that governance actions must follow a standardized and legible format, including a URL hosting an immutable document and a corresponding hash, and must provide sufficient rationale including a title, abstract, justification, and supporting materials.
This governance action includes a valid URL and hash, which matches the hash of the off-chain documentation referenced. The rationale also meets the minimum content specified in this section.
ARTICLE II, Section 7 specifies that Treasury Withdrawal governance actions must include the following:
1. Purpose, Delivery Period, Costs, and Refund Conditions
This governance action specifies:
- The purpose of the withdrawal as "This proposal strengthens Cardano’s smart contract platform across three critical and closely connected areas: language capabilities, formal correctness, and developer experience."
- Under the heading "Deliverables and Roadmap" the period for delivery of the proposed activities is between Q3 2026 and Q2 2027
- The relevant costs and expenses under the heading "Budget"
- The circumstances under which funds may be refunded to the Cardano Treasury as "All funds not disbursed by the end of the delivery period will be returned to the Cardano Treasury. A final reconciliation will be published as part of the oversight reporting cycle. In the event of partial delivery or scope reduction, unspent funds associated with cancelled or reduced deliverables will be returned proportionally."
These elements fulfil the requirements of Article II, Section 7(1).
2. Prior Treasury Funding Disclosure
ARTICLE II, Section 7(2) requires disclosure of whether the prospective recipient has received ada from the Cardano Treasury within the last 24 months.
This governance action states that "IO and its affiliated entities has been accountable for delivery of work funded by the Cardano Treasury. The total funds allocated has been ₳130,708,860 across a number of projects...". This fulfils the requirement of ARTICLE II, Section 7(2).
3. Net Change Limit (NCL)
ARTICLE II, Section 7(3) requires that Treasury Withdrawals must not exceed the Net Change Limit.
The Net Change Limit in effect at the time of submission of this vote on-chain is the governance action with ID "gov_action1m3x...4jsr7q".
- A. Current NCL Amount: 350000000 ada
- B. Current NCL Time Period: Epoch 613 to Epoch 713 (Inclusive)
- C. Total of Treasury Withdrawals within the Current NCL Time Period: 67842000 ada
- D. Amount of this Treasury Withdrawal: 11877575 ada
- E. "C" plus "D" = 79719575 ada
- F. "A" minus "E" = 270280425 ada
As the value of "F" is greater than or equal to zero, this governance action fulfils the NCL requirement.
4. Audit Allocation and Oversight Metrics
ARTICLE II, Section 7(4) states "Treasury Withdrawals actions shall require an allocation of ada as a part of such funding request to cover the cost of periodic independent audits and the implementation of oversight metrics as to the use of such ada."
This governance action states that "Acceptance of the work will be supported by a 3rd Party Assurer, who will be responsible for reviewing and signing off the work completed at each project milestone against the corresponding milestone deliverables detailed within the Legal Contract. This work is funded from a portion of this treasury withdrawal.", which fulfils the requirements of ARTICLE II, Section 7(4).
5. Designated Administrators
ARTICLE II, Section 7(5) requires that one or more administrators are designated to monitor fund usage and ensure deliverables are achieved.
This governance action states that "A written off-chain Legal Contract will be created between Input Output and the Cardano Development Holdings (CDH), as mandated by the Constitution, and will be administered by Intersect.", which fulfils this requirement.
6. Fund Management Requirements
ARTICLE II, Section 7(6) states "Any ada received from a Cardano Blockchain treasury withdrawal, so long as such ada is being held by an administrator prior to further disbursement to the Treasury Withdrawal Recipient, must be kept in one or more separate accounts that can be audited by the Cardano Community, and such accounts shall not be delegated to an SPO but must be delegated to the predefined abstain voting option."
This governance action specifies the following withdrawal address, which at the time of assessment is not delegated to an SPO and is delegated to the auto abstain voting option:
- stake17xzc8pt7fgf0lc0x7eq6z7z6puhsxmzktna7dluahrj6g6ghh5qjr
Finally, the guardrails that require consideration for this governance action are TREASURY-01a, TREASURY-02a, and TREASURY-03a. These are addressed as follows:
- TREASURY-01a - The net change limit with governance action ID "gov_action1m3x...4jsr7q" is currently in effect, after being "agreed by the DReps via an on-chain governance action with a threshold of greater than 50% of the active voting stake".
- TREASURY-02a - As per the above assessment, this treasury withdrawal does not exceed the current Net Change Limit.
- TREASURY-03a - This treasury withdrawal is denominated in ada.
We therefore find this governance action Constitutional.
This governance action sufficiently fulfils the criteria specified for treasury withdrawals in the Cardano Constitution, so is deemed constitutional.
- KtorZ64f97568…3a49YesExpired · term ends epoch 653Rationale
Okay, with remarks.
Disclaimer: given the similarities in templates between all proposals from the Input Output Group, I have will re-use the same rationale even though each proposal has been assessed independently, rather than repeating the same points 9 times.
All 9 proposals are compliant with the constitution although it is worth underscoring that:
Many specified budgets are rather imprecise and allow a lot of undefined work that cannot be clearly assigned to a deliverable.
While third party audits are mentioned, no frequency, scope or designated auditor are specified. Plus, audits from previous withdrawals are nowhere to be seen, which raises more questions when it comes to future audits...
Some proposals such as the "IO & Midgard Labs: L2 Scalability Initiative" contain highly speculative and forward-looking claims that have yet to be proven yet are presented as truth without sufficient data to back them up.
However, given the timing of my vote (i.e. quite late in the voting period), there is not much point arguing about those points that have already been visibly discussed by DReps.
- Phil_uplc68bb0b42…8746YesActive · term ends epoch 799Rationale
- Tingvard646d1b3a…be43YesActive · term ends epoch 726Rationale
Tingvard judges the “IO & VacuumLabs: Enhancing Plutus - Performance, Correctness, and Usability” treasury withdrawal governance action constitutional.
This governance action satisfies the procedural requirements for a treasury withdrawal under Article II, Section 6 and Article II, Section 7.
The proposal includes a title, abstract, rationale, supporting materials, and specifies the purpose, delivery period, costs, oversight structure, refund conditions, and prior treasury receipts as required under Article II, Section 7, §1 and §2.
The proposal defines administrators responsible for monitoring and disbursement of funds through Intersect-managed smart contracts and oversight structures, satisfying Article II, Section 7, §5.
The proposal allocates funding for audits, assurance, and oversight mechanisms, satisfying Article II, Section 7, §4.
The proposal further states that treasury-controlled accounts will not delegate to SPOs and will delegate only to the predefined auto-abstain DRep option, satisfying Article II, Section 7, §6.
The governance action states that the withdrawal is denominated in ada and does not exceed the active Net Change Limit at the time of submission, in accordance with TREASURY-02a and TREASURY-03a.
The proposal also includes references to immutable hosting and document hashing in accordance with Article II, Section 6, §1.
Tingvard therefore finds that the governance action procedurally satisfies the constitutional requirements applicable to treasury withdrawal governance actions.Tingvard finds this governance action constitutional.