The Cardano blockchain is restructuring how its core protocol gets built. Instead of one company — IOG — driving most of the engineering, the work is being split across multiple independent teams, with governance guardrails to keep things from fragmenting. The move is part of a long-term push to decentralize decision-making and implementation of the base protocol, balancing redundancy, peer review, and competition for ideas.
Two scaffolds for the transition
The shift rests on two main structures. The first is CIP-1694, a governance blueprint that lays out on-chain roles: delegators, delegate representatives, and a constitutional committee. The second is Intersect, a member-based organization that coordinates working groups, publishes requests for proposals (RFPs), and makes sure standards are met for core development. The Cardano Foundation keeps its non-profit mandate — standards, education, and network health metrics — while IOG still handles research and novel protocol work. But the long-term direction pushes more core repositories and maintenance to independent teams.
What's being split and who's doing it
Core components now being carved out include the node (networking, consensus, ledger), the smart contract stack (Plutus, Marlowe), the wallet stack, and the release process. Independent teams have already contributed notable pieces: Mithril, a fast-bootstrapping layer, and Hydra, a state-channel stack, both improve the network without touching consensus directly. Under the new model, multiple teams implement while a steering group approves interfaces and releases. Testing shifts to shared test harnesses and open RFPs for audits.
How the rhythm changed
The vibe has shifted from 'wait for IOG' to 'which working group owns the spec and test harness.' RFPs now take longer but come with predictable review gates. Exchanges, the main downstream consumers, have been asking for clearer upgrade calendars and minimum versions — a sign that coordination remains a make-or-break factor. The new structure aims to provide that clarity, but it's still early.
The unresolved question: can a decentralized group of teams keep the release train on time, or will the added layers of governance slow things down just when the network needs to move faster?
