Cardano has published a clearer, two-phase roadmap for its Dijkstra-era scaling work, centering on protocol upgrades called Ouroboros Leios and Ouroboros Peras. The plan lays out technical milestones rather than claiming any immediate adoption windfall — a reminder that this is about engineering direction, not one-billion-user arrival. What’s on the timeline - Phase 1 (target: Q4 2026): Linear Leios and nested transactions. The team expects code completion for this phase in the fourth quarter of 2026. - Phase 2 (target: Q2 2027): Ouroboros Peras, aimed at improving settlement and finality behavior, with a planned rollout in the second quarter of 2027. Why this matters technically Cardano’s Dijkstra-era work is not marketing copy — it’s a technical roadmap that seeks to increase throughput and improve how transactions are structured and settled across the base layer. Ouroboros Leios focuses on changing how transactions and block processing scale so the network can handle more activity while preserving the assumptions behind Cardano’s consensus. If realized, Leios would enable more demanding applications and a larger user base, but it is not live today and significant engineering, testing, and review remain. Nested transactions, part of the first phase, could reduce developer friction by giving more flexibility in transaction composition and execution. That’s important for complex use cases in DeFi, identity, payments, and multi-step workflows where current patterns can feel restrictive compared with faster-moving ecosystems. Ouroboros Peras, scheduled in the second phase, targets settlement and finality improvements. Better finality can make the network feel snappier and more dependable for financial applications, but as with Leios, Peras is a planned upgrade with a timeline, not a guarantee. Cardano’s development style and what it implies Cardano’s approach is research-heavy and deliberate: formal naming, peer-reviewed designs, and staged implementations. This can make progress seem slower than some rivals, but it reflects a priority on correctness and long-term architecture over short-term throughput headlines. The Dijkstra-era roadmap fits that pattern: a multi-step, protocol-level strategy rather than piecemeal band-aids. What to watch - Execution against the roadmap’s milestones (code completion, testing, peer review, deployment). - Whether nested transactions and Leios produce measurable throughput and developer UX gains. - Whether Peras delivers perceptible improvements in finality and settlement for real-world apps. - Broader ecosystem adoption factors — developers, liquidity, applications and users — which the roadmap alone cannot guarantee. Who should care - ADA holders: the roadmap signals continued investment in base-layer throughput and architecture. - Builders: the upgrades could make complex applications easier to build and more performant if implemented as intended. - The broader market: this is a technical progress story, not an adoption headline. Bottom line Cardano has mapped a structured path toward greater scale, but the value of that map depends on execution. The Dijkstra-era roadmap clarifies intentions and timelines (Q4 2026 for Leios/nested transactions; Q2 2027 for Peras), yet the community will need to see working code, rigorous testing, and real usage before declaring those ambitions realized. This article is based on Cardano roadmap materials and public technical discussions around the Dijkstra era, Ouroboros Leios, and Ouroboros Peras. Written by the News Desk and edited by Samuel Rae. Report sourced from primary documentation disclosures. Read more AI-generated news on: undefined/news