Cardano Hands Core Development to Independent Teams

One repo owner. One bottleneck. If you’ve shipped software, you know that story. Cardano’s trying a different ending.

Instead of a single company pushing core updates, the network is moving core protocol work to multiple independent teams, with governance guardrails to keep it cohesive. That’s a big cultural shift for a chain known for peer-reviewed research and careful rollout.

So what actually changes when the people writing the node, the ledger rules, and the tooling aren’t all under the same roof?

Editor's note: In Q1–Q2 2026 I kept a close eye on Cardano’s repos and governance forums while talking with two independent teams bidding on wallet and ledger work. The vibe shifted from “wait for IOG” to “which working group owns the spec and test harness.” Release notes and conformance suites mattered more than branding. A few RFPs took longer than bidders hoped, but the teams I spoke with liked the predictable review gates. From a market structure angle, exchanges mainly asked for clearer upgrade calendars and minimum versions, which tells me the coordination piece is still the make-or-break factor. — Darnell Whitaker

Cardano’s next phase focuses on decentralizing not just block production, but decision-making and implementation of the base protocol. Historically, Input Output Global (IOG) drove most of the core engineering, while the Cardano Foundation and EMURGO handled ecosystem and enterprise efforts. Now, the plan is to spread core duties across independent teams operating under clearer governance standards.

The shift aims to replace single-vendor velocity with a federation of specialized teams, balancing redundancy, peer review, and competition for ideas.

Two scaffolds support the transition. First, the governance blueprint known as CIP-1694 outlines how on-chain governance should look in practice, including roles for delegators, delegate representatives, and a constitutional committee. The spec lives in Cardano’s CIP repository and has been a community touchstone for the move to the so-called Voltaire era (GitHub CIPs).

Second, Intersect, a member-based organization formed to steward Cardano’s long-term governance and development, is taking on coordination duties, funding streams, and working groups (Intersect). The Cardano Foundation continues to push standards, education, and network health metrics from its non-profit mandate (Cardano Foundation).

How Cardano Got Here: From IOG to a Multi-Team Model

Cardano’s base layer is the product of years of research-first development. That paid off in reliability, but it also meant one company carried most of the operational burden. Community proposals, meetups, and governance experiments built pressure for a broader tent. Intersect launched to formalize that tent, creating forums and working groups that sit between raw community sentiment and actual code changes.

Governance groundwork

CIP-1694 sketched the mechanics for how the community, elected representatives, and a constitutional committee can propose and ratify changes to the protocol. It’s not just a whitepaper; it’s a set of interfaces for how decisions flow into implementation, audits, and release tracks (GitHub CIPs).

Organizations and roles

IOG still matters, especially on research and novel protocol work. But the long-term direction pushes more core repos, components, and maintenance tasks to teams that aren’t beholden to a single roadmap. Intersect’s role is to coordinate, publish RFPs, and ensure standards are met. The Cardano Foundation keeps its focus on stewardship, documentation, and ecosystem reliability checks.

On the tooling side, components like Mithril, a fast-bootstrapping and verification layer for Cardano nodes, show how independent teams can ship improvements without touching consensus directly (Mithril). Similarly, Hydra, Cardano’s isomorphic state-channel stack, evolves alongside core dev while targeting scalability at the edge (Hydra).

Who Does What: Splitting the Core Protocol

When people say “core,” they usually mean the node (networking, consensus, ledger), the compiler and languages (Plutus, Marlowe), the wallet stack, and the release process. Splitting those responsibilities must be done carefully so users don’t feel the seams.

Technical steering and ownership

Think of a technical steering function that sets compatibility requirements, testing standards, and release gates, while implementation teams compete or collaborate to meet them. Intersect’s working groups and committees are designed to formalize that function (Intersect).

Old model vs new model

Area Old Model (IOG-led) Emerging Model (Multi-team) Node & Ledger Rules Primarily engineered and merged by IOG Multiple teams implement; steering group approves interfaces and releases Smart Contract Stack Plutus/Marlowe roadmaps centralized Language/runtime owned by domain teams; backward-compatibility checkpoints Testing & QA Internal pipelines, community testnets Shared test harnesses; open RFPs for audits and fuzzing Funding & Mandates Budgeting inside core companies RFPs, grants, and on-chain-approved mandates via Intersect governance Standards & Docs Mixed ownership, ad hoc processes Foundation-led standards with community review and versioned specs

Governance Rails: Proposals, Reviews, and Funding

Decentralizing development doesn’t work without rails. The rails are how ideas become code and then policy.

How a change could flow

1. An idea is drafted as a Cardano Improvement Proposal or a scoped RFP from a working group.
2. Stakeholder feedback lands in public repos and governance forums, with delegate representatives weighing in per CIP-1694 roles.
3. Intersect coordinates independent reviews, sets testing requirements, and solicits bids from qualified teams.
4. Funding is allocated through pre-defined programs or on-chain decisions tied to governance milestones.
5. Implementation proceeds in the open; testnets pick up experimental flags.
6. A release candidate goes through security reviews and backwards-compatibility checks.
7. Governance confirms the release, and SPOs upgrade on a scheduled cadence.

None of this removes IOG’s influence; it just creates room for others to earn influence by shipping quality work under shared standards. The structure is visible in the public CIP repo and Intersect materials (GitHub CIPs, Intersect).

From Idea to Mainnet: Shipping Without a Single Boss

The obvious fear is chaos. Multiple teams, moving parts, and no single boss can turn into gridlock. Cardano’s answer is to make the release pipeline boring, predictable, and audited.

Testnets and release tracks

Cardano keeps several test tracks live. Preview for breaking changes. Preprod for near-mainnet behavior. Specialized tracks for governance trials have been used to exercise on-chain processes before they touch mainnet. The point isn’t the labels; it’s the idea that every change must survive multiple environments before SPOs are asked to upgrade.

Safety nets: Hydra and Mithril

Hydra gives builders a way to scale user flows without waiting on base-layer upgrades. That buys time and reduces pressure to jam risky changes into the node just to meet throughput demands.

Mithril helps nodes bootstrap fast and verify snapshots securely, which matters when a release is pushed and many operators need to sync from scratch. It’s also an example of a discrete subsystem evolving with its own roadmap while staying within network-wide security assumptions (Mithril).

Combined, these make it easier for independent teams to ship improvements in their lane without destabilizing consensus.

Implications for Builders, Exchanges, and Users

For developers, multiple core teams can mean more frequent, targeted releases. Language updates might move independently from networking tweaks, and tooling gaps can be closed by specialized shops responding to RFPs.

Builders

The upside is speed on the edges and clearer specs. The catch is fragmentation risk. If two teams interpret an interface differently, your dapp might run fine in testing and choke under a minor patch. That’s where standards, conformance tests, and formal release notes become non-negotiable.

Exchanges and custodians

Operationally, you’ll want to watch release cadences and deprecation schedules closely. With more teams shipping, the calendar gets busier. Expect stronger communication from the Cardano Foundation on upgrade windows and minimal supported versions (Cardano Foundation).

Everyday users

Most users shouldn’t notice much beyond wallet and dapp updates arriving a bit more often. The bigger story is resilience: if one team runs into a delay, others can keep the pipeline moving.

Milestones to Watch Over the Next Year

If you’re tracking the handoff, here are the practical markers that signal real progress.

Milestone What to look for Why it matters Constitutional/committee formalization Clear documentation of governance roles and veto/approval powers under CIP-1694 Defines who can block or greenlight changes Independent RFP awards Intersect publishes winners for core components (e.g., wallet API, ledger rules) Proof that funding ties to shipped code, not just proposals Repo stewardship diversification Maintainer files show more non-IOG ownership across key repos Signals true decentralization of code paths Coordinated mainnet release Multi-team features land in one predictable upgrade without breakage Validates the governance and testing pipeline Security reviews cadence Regular third-party audits and fuzzing reports posted before releases Keeps decentralization from weakening security

Risks & What Could Go Wrong

• Interface drift. Two teams implement the same spec in subtly incompatible ways, causing dapps to misbehave.
• Governance deadlock. A proposal gets stuck between committees and delegates, slowing urgent fixes.
• Funding mismatch. Critical maintenance loses out to flashy features in RFP cycles.
• Security regressions. More merges and faster cadences increase the attack surface without matching audit depth.
• Operator fatigue. SPOs face more frequent upgrades and unclear minimum versions, risking chain split events.
• Blame diffusion. When something breaks, owners are unclear, slowing incident response.

Decentralization isn’t free. Without disciplined specs, strong testing, and clear ownership, multi-team development can trade single-point failure for many small ones.

If you want an ongoing pulse on how the handoff is landing in practice, we track Cardano’s governance proposals, testnet releases, and team updates in our reporting at Crypto Daily.

Frequently Asked Questions

Is IOG stepping away from Cardano?

No. IOG remains a key research and engineering contributor. The change is about broadening core development so multiple independent teams can own pieces of the stack under shared standards, rather than a single vendor doing most of it.

What is CIP-1694 and why does it matter here?

CIP-1694 is a governance specification that outlines how Cardano stakeholders, delegates, and a constitutional committee interact to approve protocol changes. It’s the policy layer that makes a multi-team development model workable.

Who coordinates the independent teams?

Intersect, a member-based organization, is positioned to coordinate working groups, publish RFPs, and help align releases. The Cardano Foundation supports with standards, documentation, and ecosystem readiness.

Will development get faster or slower?

Both can happen. Independent teams can parallelize work and speed up targeted features, but governance and compatibility checks can add time to final releases. Over time, a predictable cadence usually emerges.

How does this affect dapp developers?

Expect clearer specs and possibly more frequent SDK updates. The tradeoff is staying current with compatibility notes and test vectors provided by the steering groups or maintainers.

What should SPOs and exchanges watch?

Watch for official release notes, minimum supported versions, and upgrade windows. With more teams shipping, communication from the Foundation and steering groups becomes more important.

Is this unique to Cardano?

No. Several networks have moved from single-company development to multi-team or foundation-led models. Cardano’s twist is the heavy use of formal specs and community-defined roles to keep consensus changes conservative.

Disclaimer: This article is provided for informational purposes only. It is not offered or intended to be used as legal, tax, investment, financial, or other advice.