IO Labs Targets $5M Annual Cardano Treasury Request as Core Teams Prepare to Spin Out

Input Output plans to reduce its annual Cardano Treasury request from approximately $30 million to about $5 million by moving engineering teams and delivery responsibilities into specialist companies outside its corporate structure. Brandon Wolf, executive vice president of IO Labs, detailed the model in a new Block//45 interview hosted by Jason Appleton, known as Crypto Crow, and Wendy O.

The interview adds a specific funding target to Input Output’s previously announced Cardano engineering decentralization plan. IO Labs would concentrate on research, applied engineering and early product validation, while the independent teams would control their own roadmaps, delivery obligations and future Treasury proposals.

Input Output’s Cardano Treasury Request Drops to $5 Million

Wolf said Input Output does not intend to maintain its current level of annual Cardano Treasury funding as engineering responsibilities move into a distributed organizational structure.

The transition covers teams working on the consensus and ledger components of the Cardano node, together with Plutus, Ouroboros Leios, Ouroboros Peras, Hydra and the wider Ouroboros architecture. Developers may continue working on the same technologies, but through companies that are legally and operationally separate from Input Output.

Under the proposed structure, Input Output’s own annual request would fall from approximately $30 million to $5 million. The independent companies could then submit separate proposals for the programs they maintain.

The $5 million figure therefore represents the planned request from Input Output or IO Labs, rather than a confirmed total budget for all Cardano core engineering. The combined cost will depend on the proposals submitted by the specialist teams and the funding decisions made through Cardano governance.

Wolf cited Mithril as an existing example of the model. Mithril uses stake based cryptographic certificates to produce verified Cardano blockchain snapshots, allowing nodes and light clients to synchronize without independently processing the complete chain history. Its development is now stewarded by Teragone Solutions, a specialist team that worked on the protocol before taking responsibility for its continued development.

Input Output’s Cardano Engineering platform describes the wider transition as a move toward engineering delivered by specialist partners working alongside IO Labs, with Intersect coordinating funding administration and delivery reporting.

A complete list connecting every Cardano component with its future company, transition date and funding amount has not yet been published.

Plutus, Leios, Peras and Hydra Move Into Distributed Delivery

Plutus is Cardano’s native smart contract platform. It provides the execution environment and development infrastructure used by decentralized exchanges, lending protocols, stablecoins, governance applications and other Cardano dApps. Input Output’s engineering platform currently lists Plutus as co-developed by IO Engineering and VacuumLabs.

Ouroboros Leios is Cardano’s consensus layer scaling design. It introduces parallel block production to increase the volume of transaction data the network can process while preserving the existing security model and final transaction ordering.

Wolf said transactions per second do not fully describe Cardano’s capacity because a single transaction can contain multiple inputs, outputs, assets and actions. He identified transaction bytes per second and block density as more precise technical measurements for the work processed by the network.

Ouroboros Peras addresses settlement speed. The protocol is designed to provide faster finality by reducing the time required before a section of the Cardano chain can be treated as confirmed.

Hydra operates at Layer 2 through off-chain state channels called Hydra Heads. Applications and groups of users can execute transactions outside the main chain and settle the resulting state on Cardano. The protocol is designed for products that require faster execution and lower transaction costs without moving final settlement away from Cardano.

The restructuring also includes parts of the Cardano node and its supporting infrastructure. Input Output has historically maintained the dominant Haskell implementation, while ecosystem teams are developing alternative infrastructure in languages including Rust and Go.

Multiple node implementations reduce dependence on a single codebase and allow separate teams to compete on performance, tooling and operational requirements. Input Output’s published engineering plan lists Bcryptic, Dquadrant, Quviq and Ensurable Systems among the partners involved in Cardano node maintenance and protocol hardening.

The spinout structure allows the developers already familiar with these systems to continue the work while moving technical ownership, company management and funding accountability beyond Input Output.

IO Labs Adds Research, AI Tools and Public Delivery Tracking

Wolf described IO Labs as the next structure for Input Output’s Cardano business unit. Its work will combine foundational research, applied engineering, prototypes and the production validation of new technologies.

Research programs would be evaluated against potential users, market demand, adoption paths and possible revenue models. IO Labs could build an initial product when Cardano lacks essential infrastructure or when a working implementation is needed to test new protocol functionality.

Wolf presented Lace as an example. Input Output developed the wallet as a user-facing product and as an environment for integrating new Cardano capabilities. External teams can examine and reuse its open-source components, while IO Labs can use the product to validate features before wider ecosystem adoption.

Input Output teams are also exploring a Cardano-specific Model Context Protocol that could connect AI models with Cardano nodes, development tools and technical documentation. Wolf said one option would integrate the protocol directly into a node or provide it as an additional component, although no final architecture or release schedule has been announced.

Developers are already using retrieval-augmented generation systems to query Cardano documentation from their working environments. Input Output also applies agent-based workflows to code review, testing, DevOps and development pipeline checks, with human review retained before software reaches production.

The company is developing an AI maturity model that measures whether these tools improve delivery speed, software quality and security. Wolf said the Lace team began using agent-based coding approximately two years ago and tracked the results through development and quality indicators.

Input Output also plans to expand its public tracking of Cardano engineering. The Cardano Engineering platform is intended to document active programs, delivery partners, completed milestones and the transfer of projects to specialist companies.

Wolf said future Input Output proposals will be presented to DReps and the wider Cardano community before their formal on-chain submission. Once the transition records and proposals are published, Treasury voters will be able to review IO Labs’ reduced research request separately from the funding sought by companies responsible for Plutus, Leios, Peras, Hydra and node infrastructure.