The ₳9.6M PFMS police evidence treasury withdrawal
PFMS: Bringing Government Scale Adoption to Cardano by Trivolve Tech
gov_action1wfy3vzxurfgq6wrpxg2qdx3t6wm7ng8xwr26h47kxa8xhd20cr5qqz0wzfcLast votes count before start of epoch 669: Nov 20, 2026, 21:44 UTC
Nov 20, 2026, 21:44 UTC
In plain English
Trivolve Tech is asking the Cardano treasury for ₳9.6M to build the Police Force Management System (PFMS): open-source software that fingerprints (hashes) and timestamps police and court records on Cardano mainnet, so anyone can later check that a piece of evidence hasn't been altered. Only the hashes go on chain; the proposal says no file contents or personal data leave the police systems.
The first deployment is planned for the Indian state of Telangana, covering five stages of a case: pre-crime evidence, investigation, evidence storage, prosecution and the courts. Trivolve says one stage (FMS) is already live on Cardano at roughly 11,000 mainnet transactions a month, projects more than 1.5 million transactions in PFMS's first year, and says the state government will pay transaction fees and run the infrastructure afterwards.
The money is released in five milestones over about 15 months: ₳1.8M at kickoff, then ₳2M at months 3, 8 and 12, and ₳1.8M at month 15. Milestones 1 to 4 are paid only after an independent assurer and the administrator verify the deliverables. The Cardano Foundation is the named administrator; funds sit in its multisig, delegated to the Always Abstain DRep option.
The proposal caps spending at USD 0.30 per ADA (USD 2.88M) and says anything above that, plus unspent ADA, returns to the treasury. It says 70% of future verification revenue would go to the treasury, 20% to core Cardano library maintenance and 10% to Trivolve Tech. It discloses about ₳1.49M of past Project Catalyst funding and no treasury withdrawals in the prior 24 months.
Who it affects
- The Cardano treasury: ₳9.6M would leave it, paid out in five milestone tranches through the Cardano Foundation as administrator.
- Trivolve Tech and its subcontractors, which build the software. The proposal says they get no development fee from the state government, only separate maintenance fees.
- The Telangana state police and justice system as the first user, and other governments that might adopt the open-source software later.
- DReps and the Constitutional Committee, who decide it. SPOs do not vote on treasury withdrawals.
Where the vote stands
Snapshot: Koios, Oct 26, 2026, 13:01 UTC, epoch 663, block 14,118,605
| Voting body | Yes | No | Abstain | Yes % of stake |
|---|---|---|---|---|
| DReps | 16 | 8 | 2 | 4.62% |
| SPOs | Not applicable SPOs do not vote on treasury withdrawals. | |||
| Constitutional Committee | 1 / 7 | 0 / 7 | 0 / 7 | — |
Yes is 4.62% of DRep voting stake when delegated stake that hasn't voted counts as No (the CIP-1694 rule). Among DReps who voted Yes or No, Yes is about 69.8% of stake (₳243.94M yes vs ₳105.55M no): most delegated stake hasn't voted yet.
1 of 7 Constitutional Committee members (Tingvard) has voted Yes, judging the action constitutional.
Counts are votes cast; percentages are stake-weighted, per CIP-1694.
What it needs to pass
- DReps: Yes must reach at least 67% of active DRep voting stake. Delegated stake whose DRep hasn't voted counts as No; Abstain votes and the Always Abstain option are left out.
- Constitutional Committee: at least two-thirds of the voting committee members must vote Yes (the committee currently has 7 members).
- SPOs: no vote on this action type.
- The withdrawal must also fit the Cardano Constitution's treasury guardrails, such as the net change limit.
- If it reaches both thresholds at an epoch boundary, it is ratified and paid out at the next boundary. If it hasn't by the start of epoch 669 (Nov 20, 2026, 21:44 UTC), it expires and the ₳100,000 deposit is returned.
Arguments for / against
We don't take sides. These are verbatim excerpts from published vote rationales and the proposal document. Follow the links to read them in full.
The case for
“Yes: real government use with an experienced team, milestone payments under Cardano Foundation oversight.”
“PFMS builds on FMS, which already covers one of the five stages and has run for over a year on the state’s own infrastructure. The team is extending a working system for a customer it already serves. … I have two reservations. The 1.8M ada kickoff tranche is large, and the 1.5M transactions a year are a projection.”
“Trivolve already has a live Forensic Management System on Cardano mainnet with a real Indian state government, generating significant transactions.”
The case against
“A company normally builds a product at its own cost and carries the risk. Here the build and the risk move to ada holders while the client relationship and the maintenance revenue stay with the vendor.”
“My decision is based on timing and responsible Treasury stewardship. … This is a vote on when to fund, not whether the project deserves funding.”
“PFMS only creates value if the government uses it beyond the funded period.”
Excerpts are taken verbatim from rationales attached to on-chain votes; follow the links to read them in full. ADAtainment discloses working at the Cardano Foundation (the action's administrator) and says the vote is their own. Both No rationales say they see merit in the project; their objections are about who carries the build cost and timing against the Net Change Limit. The last 'concern' is from the proposal's own risk section.