IO & Ensurable Systems: Cardano Maintenance Initiative
**Proposal as pdf: [https://ipnso-com.ipns.dweb.link/?cid=QmYKV7vbX9pwNxst2qWpmtM2k6LRJB4NKKNFJSQyh7zojz](https://ipnso-com.ipns.dweb.link/?cid=QmYKV7vbX9pwNxst2qWpmtM2k6LRJB4NKKNFJSQyh7zojz)** Every feature, upgrade, and innovation proposed for Cardano depends on a stable, secure, and well-maintained platform underneath. This proposal funds that foundation — continuous core maintenance and operational support from Q3 2026 through Q1 2027. Maintenance is not discretionary. It covers nine functional areas that together constitute the full support envelope for Cardano: bug fixing and security reviews, CI/CD and infrastructure operations (including disaster recovery per CIP-135), mainnet and mempool monitoring, the Cardano Blueprint documentation project, open-source community support, systematic performance analysis and optimization, quality assurance and release sign-off, full node release management with L1/L2/L3 incident response, and component maintenance across Plutus Core, DB-Sync, guardrails scripts, APIs, and CLI tools. The value is both protective and enabling. On the protective side, this work ensures network uptime, swift incident resolution, and proactive security hardening through collaboration with the Intersect Security Council. On the enabling side, it delivers the Cardano Blueprint — implementation-independent specifications that lower the barrier for alternative node implementations — and continuous performance optimization that safeguards throughput gains and release quality. IO is collaborating with Ensurable Systems to distribute infrastructure stewardship. Intersect administers funds through milestone-based smart contracts with independent third-party assurance and transparent on-chain dashboards. Unspent funds return to the Treasury. **Treasury Ask:** ₳62,134,630
Reasoning
Written after the vote was cast
What this asks for, and from whom
IO and Ensurable Systems asked for 62,130,000 ADA for the Cardano Maintenance Initiative, continuous core maintenance and operational support across nine functional areas from Q3 2026 through Q1 2027.
What would have to be true for this to be a good use of treasury funds
Somebody has to keep the platform running. Every feature and upgrade anyone proposes depends on a stable, maintained base underneath, and maintenance is not discretionary work that can wait for a better market.
What specifically concerns me
Sixty-two million ADA is one of the largest single line items I have ever voted on, and concentration of core maintenance in one vendor is a real long-term risk to decentralization. I voted yes because the alternative to imperfect, expensive maintenance is not cheaper maintenance, it is degradation of the thing everything else stands on. But the size means the reporting bar is high.
What I am asking of the proposer if this passes
It was enacted. Publish what the nine functional areas actually delivered, quarter by quarter, in terms the community can check. And keep working toward more client diversity so this line item is not permanently sole-sourced.