Cardano’s governance body Intersect has laid out a detailed roadmap for the blockchain’s next major era, splitting the Dijkstra upgrade into two phases rather than a single hard fork. Phase 1 is penciled in for Q4 2026, with Phase 2 following in Q2 2027.
The plan, unveiled on August 16, 2026, arrives just weeks after the successful van Rossem hard fork in mid-July. That upgrade, which moved Cardano to Protocol Version 11, was essentially the foundation pour for everything Dijkstra promises to build on top.
What Phase 1 actually changes
The headline feature of the first phase is Ouroboros Linear Leios, formally tracked as CIP-164. Linear Leios is a scaling mechanism designed to put idle node capacity to work. Linear Leios introduces two new block types, Ranking Blocks and Endorser Blocks, that allow the network to process additional endorsed transactions during those idle periods.
Phase 1 also brings Nested Transactions, documented as CIP-118. This feature allows transactions to contain other transactions within them, which is a practical improvement for composability. DeFi protocols, in particular, benefit from being able to bundle complex multi-step operations into a single atomic transaction.
Both features arrive alongside what Intersect describes as “critical ledger updates.”
Phase 2 and the Peras hard fork
The second phase, targeted for Q2 2027, introduces Ouroboros Peras via an intra-era hard fork. Unlike a full-era transition, an intra-era hard fork upgrades the protocol within the same governance era, which means it doesn’t require the kind of sweeping constitutional changes that accompanied previous era transitions.
Peras, tracked as CIP-140, redesigns the voting mechanism that validators use to confirm blocks. The goal is faster transaction settlement. Peras aims to compress the finality window by introducing a more efficient voting round among stake pool operators, letting transactions reach irreversible status more quickly.
Governance gates and timeline caveats
Intersect was careful to frame these dates as estimates, not commitments. Cardano’s post-Conway governance model, established through CIP-1694, requires multiple layers of community approval before any protocol change can go live.
Delegated Representatives, known as DReps, must vote to ratify upgrades. So must stake pool operators and the Constitutional Committee.
The development itself is proceeding on two parallel tracks. The established Haskell node client continues to serve as the primary implementation, but a Rust-based client is also in development with a target of producing mainnet blocks around November 2026. Running two clients written in different programming languages is a resilience strategy: if a bug in one client causes issues, the other can keep the network running.
The Rust client timeline is notable because it overlaps with Phase 1’s Q4 2026 window. If both milestones land on schedule, Cardano would enter 2027 with meaningfully upgraded throughput capacity and a more robust node infrastructure.
Disclosure: This article was edited by Editorial Team. For more information on how we create and review content, see our Editorial Policy.

6 days ago
33







English (US) ·