{ "@context": { "@language": "en-us", "CIP100": "https://github.com/cardano-foundation/CIPs/blob/master/CIP-0100/README.md#", "CIP136": "https://github.com/cardano-foundation/CIPs/blob/master/CIP-0136/README.md#", "hashAlgorithm": "CIP100:hashAlgorithm", "body": { "@id": "CIP136:body", "@context": { "references": { "@id": "CIP100:references", "@container": "@set", "@context": { "GovernanceMetadata": "CIP100:GovernanceMetadataReference", "Other": "CIP100:OtherReference", "label": "CIP100:reference-label", "uri": "CIP100:reference-uri", "RelevantArticles": "CIP136:RelevantArticles" } }, "summary": "CIP136:summary", "rationaleStatement": "CIP136:rationaleStatement", "precedentDiscussion": "CIP136:precedentDiscussion", "counterargumentDiscussion": "CIP136:counterargumentDiscussion", "conclusion": "CIP136:conclusion", "internalVote": { "@id": "CIP136:internalVote", "@container": "@set", "@context": { "constitutional": "CIP136:constitutional", "unconstitutional": "CIP136:unconstitutional", "abstain": "CIP136:abstain", "didNotVote": "CIP136:didNotVote", "againstVote": "CIP136:againstVote" } } } }, "authors": { "@id": "CIP100:authors", "@container": "@set", "@context": { "did": "@id", "name": "http://xmlns.com/foaf/0.1/name", "witness": { "@id": "CIP100:witness", "@context": { "witnessAlgorithm": "CIP100:witnessAlgorithm", "publicKey": "CIP100:publicKey", "signature": "CIP100:signature" } } } } }, "hashAlgorithm": "blake2b-256", "body": { "govActionId": "gov_action1wfy3vzxurfgq6wrpxg2qdx3t6wm7ng8xwr26h47kxa8xhd20cr5qqz0wzfc", "summary": "Tingvard judges the “PFMS: Bringing Government Scale Adoption to Cardano by Trivolve Tech” Treasury Withdrawal governance action constitutional.", "rationaleStatement": "This governance action requests 9,600,000 ADA from the Cardano Treasury to fund the design, development and deployment, over 15 months, of the Police Force Management System (PFMS). PFMS is an open-source evidence layer developed by Trivolve Tech that records cryptographic fingerprints of police and justice records on Cardano mainnet, with an Indian state government as its first deployment. The Cardano Foundation is named as administrator.\n\nThis action is properly framed as a Treasury Withdrawals action and must therefore be assessed under Article II, Section 6 and Article II, Section 7 of the Constitution, together with the applicable treasury guardrails in Appendix I.\n\nThe action satisfies Article II, Section 6, §1. The anchored metadata is hosted on IPFS, which is content-addressed, so the document hosted at the anchor URL cannot be altered after submission. The document matches its on-chain hash. The on-chain withdrawal amount, destination account and guardrails script hash are identical to those stated in the anchored metadata. The referenced proposal documents are also hosted on IPFS, so their content is fixed by their content identifiers.\n\nThe proposal satisfies Article II, Section 6, §2. It includes a title, abstract, motivation, a detailed rationale, a budget, milestones, a risk discussion and supporting materials.\n\nThe proposal satisfies Article II, Section 7, §1. The anchored metadata identifies the purpose of the withdrawal and a delivery period of 15 months. It sets out the relevant costs and expenses in a budget of eight line items adding up to 9,600,000 ADA, and a payment schedule of five milestone tranches. It states the circumstances under which funds are returned to the Cardano Treasury: unspent ada at programme end, material milestone failure, fraud and scope abandonment. It also caps project expenditure at USD 0.30 per ADA, with any value above that cap returned to the Treasury, and states that all funds not disbursed by the end of the delivery period are returned.\n\nThe proposal satisfies Article II, Section 7, §2. It states that Trivolve Tech and its subcontractor have not received ada from the Cardano Treasury through a Treasury Withdrawal in the prior 24 months, and separately discloses approximately 1.49 million ADA of Project Catalyst funding across Fund 12 and Fund 14.\n\nThe action satisfies Article II, Section 7, §3 and TREASURY-01a and TREASURY-02a. The applicable Net Change Limit of 500,000,000 ADA covering epochs 613 to 713 has been agreed on-chain, and the enacted withdrawals in that period leave sufficient remaining capacity for this request, together with the other Treasury Withdrawals currently pending. The withdrawal is denominated in ada, satisfying TREASURY-03a.\n\nThe proposal satisfies Article II, Section 7, §4, with a concern. It allocates 480,000 ADA to project management and audit and 200,000 ADA to administration. It provides for a competitively procured independent third-party assurer that will review the delivered work and conduct independent audits at M1, M2, M3 and M4, funded from the same allocation as the oversight metrics. As in the “5am.earth Trust Layer Targeting Vision 2030 KPIs” ruling, an assurer selected after approval is acceptable where the administrator is designated and the assurer’s role and audit points are specified. However, the audit cost is combined with the recipient’s own project management in a single line item, and the assurer is to be procured within the recipient’s own work package.\n\nThe proposal satisfies Article II, Section 7, §5. It states that “The Cardano Foundation is the named administrator of this proposal.” The designation is unconditional, covers the full delivery period, and names an administrator independent of the recipient. The Cardano Foundation is also listed as a co-author of the anchored metadata, and the withdrawal destination is an account the Cardano Foundation has used in its earlier governance actions. Milestone tranches after the first are released only after the deliverables have been verified by the independent assurer and the administrator.\n\nThe action satisfies Article II, Section 7, §6, with a concern. The provision requires that ada held by an administrator prior to further disbursement be kept in one or more separate accounts that can be audited by the Cardano Community, not delegated to an SPO, and delegated to the predefined abstain voting option. Tingvard verified on-chain at epoch 662 that the destination account identified in the action is publicly auditable, is not delegated to an SPO, and is delegated to the predefined abstain voting option.\n\nHowever, the anchored metadata states that withdrawn funds “are held by the administrator’s multi-sig wallet address”. The destination identified in the action is an ordinary key-based address, and there is no on-chain multisignature script. The account is also the account to which the Cardano Foundation’s governance action deposits have been returned, including the deposit for this action, rather than an account dedicated to these funds. Article II, Section 7, §6 does not require a multisignature arrangement, and the account identified meets each of the requirements the provision sets out. Tingvard therefore does not find a constitutional defect. The custody description in the metadata is nonetheless inaccurate, and the requirements of Article II, Section 7, §6 continue to apply for as long as the administrator holds the funds, including in any hedging arrangement.\n\nTingvard also notes that the metadata states it “embeds the blake2b-256 hash” of the proposal document, but no such reference hash is included. Because the referenced documents are hosted on IPFS, their content is nonetheless fixed, and this inaccuracy does not affect the assessment.\n\nTingvard has considered Article I, Section 1, Tenets 3, 6, 8 and 9. The funded software is to be released as open source, and Tingvard does not find a clear, objective failure under any of the Tenets.\n\nTingvard therefore finds that the proposal satisfies the applicable constitutional requirements for a Treasury Withdrawals action.", "precedentDiscussion": "This decision is consistent with prior Tingvard assessments of treasury withdrawals where the constitutional review focuses on whether the proposal provides clear withdrawal terms, a delivery period, cost basis, prior funding disclosure, audit and oversight structure, administrator designation, custody protections, refund conditions, and Net Change Limit compliance.\n\nIt also illustrates the standards Tingvard applied in its rulings on the “Cardano Strategic Copper Reserve” and “AURORA” actions. This action is anchored on content-addressed storage, states the terms required by Article II, Section 7 in its own metadata, and references its supporting documents through content identifiers that fix their content.\n\nThis decision clarifies that Article II, Section 7, §6 is assessed against the account identified in the action, as Tingvard held in the “Governance Incentives Framework 2026” ruling. Where that account meets the requirements of the provision, an inaccurate description of additional custody arrangements, such as a multisignature wallet, is not in itself a constitutional defect. Tingvard approved the “Cardano x Draper Dragon: Orion Fund” action, whose destination was also a key-based account. Tingvard nonetheless expects administrators to describe custody arrangements accurately, and to use accounts dedicated to the treasury funds they hold.\n\nThis decision also preserves the distinction between constitutional review and policy review. Whether Cardano should fund a policing and justice evidence system, whether 1,800,000 ADA should be released on contract signing before any deliverable, whether the confidential state agreements viewed only by the administrator give DReps enough information, whether the projected transaction volumes and the revenue-sharing commitment are realistic, how the ADA price hedging will be carried out, and whether the request represents value for money are questions for DReps and ada owners. The revenue-sharing commitment concerns revenue from third parties, not treasury funds, and Tingvard does not treat it as a constitutional safeguard. The CC assessment is limited to whether the action conflicts with the Constitution.", "counterargumentDiscussion": "One possible counterargument is that the action misdescribes its custody arrangement. The metadata refers to a multi-sig wallet, while the destination has no on-chain multisignature script and is the administrator’s general governance account. On this view, the custody described is not the custody that exists, and Article II, Section 7, §6 should be found unsatisfied.\n\nTingvard acknowledges that this is the strongest argument against constitutionality. However, Article II, Section 7, §6 sets out specific requirements: separate accounts that can be audited, no delegation to an SPO, and delegation to the predefined abstain voting option. The account identified in the action meets each of them, and Tingvard has verified this on-chain. The provision does not require a particular signing arrangement, and Tingvard does not add one. At the time of review the account held no other funds of significance, and every movement into and out of it is publicly traceable. Tingvard records the inaccuracy so that DReps can take it into account.\n\nAnother possible counterargument is that the independent assurer has not yet been appointed, and that it is to be procured within the recipient’s own work package.\n\nTingvard does not find this unconstitutional. The administrator is designated, the assurer’s role and audit points are specified, the procurement is to be published, and no milestone tranche after the first is released without verification by both the assurer and the administrator.\n\nA further concern is that the refund provisions for fraud, scope abandonment and material milestone failure are brief, and in some cases state only that undisbursed tranches will not be released. Article II, Section 7, §1 requires the circumstances under which the withdrawal might be refunded to be stated, and they are. The adequacy of the mechanics is a matter for DReps.", "conclusion": "Tingvard finds the “PFMS: Bringing Government Scale Adoption to Cardano by Trivolve Tech” Treasury Withdrawal governance action constitutional.\n\nThe action is anchored on content-addressed storage and identifies the purpose, delivery period, costs, refund circumstances, prior funding disclosure, Net Change Limit position, audit and oversight allocation, named administrator, and an account that meets the custody and delegation requirements.\n\nThis finding relies on the destination account remaining compliant with Article II, Section 7, §6. If, before ratification, the destination account is delegated to an SPO or ceases to be delegated to the predefined abstain voting option, Tingvard will change its vote to unconstitutional.\n\nTingvard therefore judges this governance action constitutional.", "internalVote": { "constitutional": 4, "unconstitutional": 0, "abstain": 0, "didNotVote": 1, "againstVote": 0 }, "references": [ { "@type": "RelevantArticles", "label": "Cardano Blockchain Ecosystem Constitution", "uri": "ipfs://bafkreieyuknozbtewyurfqoagvplvykadn6a4u6wglupavdz46bbsnnl6e" } ] }, "authors": [ { "name": "Tingvard", "imageUrl": "ipfs://QmPkHXdK6GLtDNyyKFBWRwARFEy9TPFcbpDganixmRXwWJ" } ] }