Cardano’s founding development company is stepping back from the code it built. Input Output (IO) confirmed on July 17, 2026 that it will begin handing control of Cardano’s core software — the Haskell node, the Plutus smart-contract platform, the Daedalus wallet, the Hydra scaling layer and developer relations — to independent engineering teams starting in August, with the transition running into 2027 (CoinDesk). The move is the last stage of the network’s Voltaire era: not just on-chain governance, but the actual maintenance of the software that runs the chain.
What Input Output is handing over
The handover is broader than a symbolic rebrand. Specialist firms Se7en Labs — a team with deep Solana infrastructure experience — and Teragone, the group that already leads development of Cardano’s Mithril signature protocol, will take ownership of specific components. The plan calls for at least three independent Cardano implementations, written in Haskell, Rust and Go, to be maintained under community oversight with formal specifications rather than a single company’s internal roadmap (Binance Square).
Governance bodies Intersect and Pragma will oversee those specifications, with changes subject to community review and voting. Input Output, in turn, says it will shift its own focus toward research and new ventures through IO Labs and IO Ventures. Founder Charles Hoskinson framed it plainly: “The last stage of the Voltaire era is full decentralization of node and reference blueprint development.”
Why the timing matters
Decentralization is usually sold as a principle. Here it reads as a response to pressure. Cardano’s total value locked sits around $70 million, while rival smart-contract chains Tron and Solana each report more than $4 billion in TVL (DefiLlama). The network’s native token, ADA, traded near 16 cents on the announcement date — roughly 95% below its September 2021 peak of $3.10. Hoskinson has acknowledged the setbacks openly, calling them “growing pains that are very uncomfortable” and warning earlier in the year that deteriorating market conditions would force many projects to shut down.
That competitive gap is the pressure behind the restructure. Cardano was once positioned as a premier smart-contract platform, but its share of developer attention and locked value has slipped while faster, EVM-compatible chains captured much of the application layer. Handing the codebase to specialist teams is an attempt to close that gap by accelerating delivery and letting multiple groups ship in parallel, rather than waiting on a single internal roadmap. It also broadens the talent pool: Se7en Labs and Teragone bring experience from outside the Cardano ecosystem, which Input Output hopes will introduce new engineering practices to the core stack.
That context is the real story. Spinning core development out to several companies reduces Cardano’s dependence on the one organization that designed it, but it also tests whether a distributed set of teams can ship coordinated upgrades without slowing down or fragmenting the protocol.
The bet and the risk
The upside is resilience: no single company becomes a bottleneck or a single point of failure for the chain’s roadmap. The risk is coordination. Multiple implementations in three languages, maintained by separate firms and reconciled through community specification, raise the chance of divergence — and of slower delivery if the groups disagree. Input Output is explicitly betting that diverse, independent maintainers produce a healthier network than centralized stewardship, even if the transition is messy.
For ADA holders and developers, the practical question is whether dapps and tooling keep working uninterrupted as control changes hands. Input Output says protocol decisions and governance have already moved to the community, so the code handover is the final piece rather than the first. If the outside teams deliver, Cardano becomes one of the few major blockchains whose core software is genuinely maintained beyond its founder’s company. If they stumble, the “growing pains” Hoskinson describes could last longer than the roadmap assumes.
