Summary: Governance Hour – IO’s Cardano Maintenance Proposal
In this episode of the “Governance Hour”, Nicolas Cerny (Governance Lead at the Cardano Foundation) speaks with Michael Karg, Performance and Tracing Team Lead at Input Output. They take a deep dive into the Treasury withdrawal governance action for Core Cardano Maintenance and Operational Support, discussing what it takes to keep the network secure, reliable, and performant.
The Engine Room of the Ecosystem
While many proposals focus on flashy new features, the maintenance and support proposal is described as the “engine room” of Cardano. It is the unsung hero work required to sustain the billions of dollars in value the network holds. The proposal requests roughly 62 million ada to fund nine months of operations (from Q3 2026 to the end of Q1 2027).
Crucially, Input Output is not doing this alone. To push for the decentralization of stewardship, they have partnered with Insurable Systems a highly qualified team with deep Cardano domain knowledge as a co-deliverer for this cycle.
Three Pillars of Maintenance
The operational work is categorized into three foundational pillars:
- Stability: Cardano has a near-perfect track record of network availability. This requires continuous monitoring, vetted releases, and a 24/7 disaster recovery rotation ready to step in at any time if an unintended chain fork or network incident occurs.
- Safety: Security and safety come from confidence in the system. This confidence is built through rigorous quality assurance, including unit testing, property testing, and extensive end-to-end conformance testing frameworks.
- Scalability: As Cardano prepares for massive upgrades like Leios and Hydra, the underlying foundation must be robust. A major part of this pillar involves actively identifying and reducing “tech debt” so that new, complex features can be implemented safely and efficiently.
Key Work Streams and Tooling
The 62 million ada budget covers a highly cross-functional effort divided into nine major work streams. This includes complex architecture bug fixing, DevOps (like running bootstrap relays and public testnets), and coordinating with the Haskell compiler team. It also funds the upkeep of critical developer tooling such as DB-Sync, the Cardano CLI, the Cardano API, and the ongoing documentation for the “Cardano blueprint”, which explicitly empowers developers to build alternative node clients.
Efficiency in Bundling
Addressing concerns about the large size of the treasury ask, Michael Karg explained that bundling these nine work streams into one proposal is the most cost-effective approach. Because the tasks require shared infrastructure and deeply intertwined domain knowledge, splitting them up would introduce significant friction and unnecessary overhead costs.
Top Five Q&A (FAQ) about the Core Maintenance Proposal
Question 1: What is the main goal of the Cardano Maintenance Proposal?
Answer: The proposal funds the essential “engine room” operations required to keep the Cardano network running securely and efficiently. It covers a nine-month period and asks for roughly 62 million ada to support continuous bug fixing, 24/7 disaster recovery, infrastructure operations, and the maintenance of core tooling like DB-Sync and the Cardano CLI.
Question 2: Who is responsible for delivering this maintenance work?
Answer: While Input Output is taking the lead for this delivery cycle, they have intentionally partnered with Insurable Systems as a co-deliverer. This partnership is a deliberate step toward the decentralization of stewardship, proving that maintenance can be successfully shared with and handled by other highly qualified entities in the ecosystem.
Question 3: Why is the requested budget bundled into one large proposal instead of several smaller ones?
Answer: The maintenance deliverables are highly interconnected and rely on cross-functional teams spanning engineering, DevOps, quality assurance, and security. Bundling them into one proposal allows the teams to share infrastructure and domain knowledge efficiently. Splitting the proposal would create operational friction and ultimately increase the total cost.
Question 4: How does this proposal enable node diversity and further decentralization?
Answer: A key deliverable is the ongoing documentation of the “Cardano blueprint”. This blueprint provides the exact technical specifications of the network down to the byte level. By maintaining this open documentation, independent developers have the exact reference they need to build their own node clients in languages like Rust or TypeScript, fostering true implementation decentralization.
Question 5: What are the risks if this maintenance proposal is not funded?
Answer: Without dedicated maintenance, the network faces severe risks. If a security vulnerability were to arise, the lack of a 24/7 incident response team could prove fatal to the network. Furthermore, without rigorous performance benchmarking and testing frameworks, protocol upgrades and new features would have to be implemented blindly, breaking the evidence-based approach that makes Cardano so secure.
Tuesday, 12 May
16:00 – 17:00 UTC