Cardano’s development roadmap for its Dijkstra-era scaling work has been structured around a two-phase rollout, with Ouroboros Leios and related throughput improvements central to the plan.
The first phase, involving Linear Leios and nested transactions, targets code completion in the fourth quarter of 2026. A second phase, involving Ouroboros Peras, is planned for the second quarter of 2027.
This is a roadmap story, not an adoption victory lap.
Cardano has long talked about scaling toward much larger user numbers, but those goals remain future ambitions. The important news here is the technical path being mapped, not proof that one billion users have arrived.
TL;DR
- Cardano’s Dijkstra-era roadmap includes a two-phase scaling plan.
- Phase 1 targets Linear Leios and nested transactions in Q4 2026.
- Phase 2, involving Ouroboros Peras, is planned for Q2 2027.
Why The Dijkstra Era Matters
Cardano’s development style is different from many other chains.
The network often moves through research-heavy phases with formal naming, peer-reviewed design, and staged implementation. That can make progress feel slower, but it also reflects Cardano’s emphasis on correctness and long-term architecture.
The Dijkstra-era roadmap fits that pattern.
Instead of only chasing short-term throughput headlines, Cardano is laying out a longer scaling path involving protocol-level changes.
For developers and users, the question is whether that path can produce practical improvements in speed, capacity, and application performance.
Leios Is The Main Scaling Piece
Ouroboros Leios is designed to improve Cardano’s throughput by changing how transaction and block processing can scale.
The goal is to let the network handle more activity without abandoning the assumptions that underpin its consensus design. If successful, Leios could support more demanding applications and a larger user base.
But it is not live yet.
The roadmap gives development targets, not completed deployment. Code completion, testing, review, and implementation all matter before users feel any effect.
That is why the timeline needs to be treated carefully.
Nested Transactions Could Improve Flexibility
Nested transactions are another part of the first phase.
They could give developers more flexibility in how transactions are structured and processed. That can matter for complex applications, especially in DeFi, identity, payments, and multi-step workflows.
Cardano has sometimes been criticized for developer friction compared with faster-moving ecosystems.
Roadmap items like nested transactions are part of the effort to reduce that friction and make the chain more useful at scale.
Peras Adds Another Layer
The second phase, involving Ouroboros Peras, is planned later.
Peras is tied to improving settlement and finality dynamics, which can affect user experience and application design. Faster or more reliable finality can make a network feel smoother, especially for financial applications.
Again, the details matter.
A planned Q2 2027 phase gives the market a timeline to track, but not a guarantee. Cardano’s community will watch whether milestones are met and whether the improvements translate into real usage.
The Measured Read
Cardano’s roadmap shows continued work on scaling, but it does not settle the adoption question.
A network can have a strong technical plan and still need developers, liquidity, applications, and users. The Dijkstra-era roadmap is one piece of that larger puzzle.
For ADA holders, the significance is that Cardano is still investing in base-layer throughput and long-term architecture.
For builders, the important question is whether the upgrades make applications easier and more powerful to build.
The ambition remains large. Now the chain has to execute phase by phase.
This article is based on Cardano roadmap materials and public technical discussions around the Dijkstra era, Ouroboros Leios, and Ouroboros Peras.
This article was written by the News Desk and edited by Samuel Rae.
This report is based on information released in disclosures at primary source documentation.
