Cardano’s long-awaited Dijkstra improve is staying on the right track — however builders are shifting gears from pure engineering to ecosystem readiness as they put together a two-phase rollout that spans 2026–2027.
What’s coming and when
– Part 1: Dijkstra ledger period with Linear Leios (the principle scaling function), Nested Transactions, new transaction/block serialization, Plutus V4 updates and a number of other protocol-parameter additions. Intersect targets code completion in This autumn 2026. Part 1 may also set up the codec extensions and parameter slots required for the following section, however it won’t activate Ouroboros Peras.
– Part 2: Ouroboros Peras, which provides an on-chain voting layer of stake-pool operator committees to speed up settlement versus customary Praos chain-depth guidelines. Peras is deliberate as an intra-era exhausting fork focused for Q2 2027 and would require its personal preview, pre-production deployments and a separate on-chain governance motion.
Key technical particulars
– Linear Leios doesn’t exchange Cardano’s Praos safety mannequin. As an alternative it introduces “Endorser Blocks” that may reference and certify further transactions through stake-based committees — a design supposed to spice up throughput whereas preserving the bottom consensus ensures.
– Nested Transactions and codec/serialization updates in Part 1 put together the ledger for Peras with out switching it on instantly.
– The van Rossem exhausting fork in July moved mainnet to Protocol Model 11 and laid foundational groundwork for Dijkstra and Leios.
Node range and Amaru (Rust node)
– Intersect highlights a push for larger node-client range. Amaru, an open-source Rust node, is already succesful as a relay and may validate and sync to the chain tip. Mainnet block manufacturing for Amaru is focused for November 2026, with growth milestones proven as: basic block-producer launch (Sept. 30), Dijkstra-compatible block producer milestone (Oct. 29) and Leios-compatible launch (Nov. 26). These are growth targets moderately than assured activation dates.
– Rising different node implementations goals to scale back reliance on the Haskell node and broaden the ecosystem.
Governance and constitutional modifications
– Some Dijkstra protocol parameters can’t be altered by on-chain governance except they’re explicitly lined by the Structure’s guardrails. Enter Output plans a narrowly scoped constitutional modification that provides these parameters and permitted ranges — with out altering governance roles, voting thresholds or constitutional ideas.
– The present plan is to submit that governance motion no later than Epoch 655 (starting Sept. 11). Neighborhood dialogue is being funneled by way of Intersect’s Constitutional Modification Portal, which had 4 preliminary submissions as of Aug. 14.
Course of and caveats
– Intersect’s Aug. 14 Weekly Replace (#124) says planning is shifting towards testnet reporting, ecosystem readiness and help for different node groups, and that the agreed technical scope and goal dates stay unchanged.
– The roadmap’s This autumn 2026 (Part 1 code-completion) and Q2 2027 (Peras activation) targets are estimates, not ensures. Testing, preview/pre-production cycles and on-chain governance can push mainnet activation later.
Why it issues
If profitable, Dijkstra’s Linear Leios and Peras collectively may materially improve Cardano’s throughput and settlement pace whereas protecting current consensus ensures intact. The timeline additionally alerts a maturation of the ecosystem — from a single Haskell reference node to a extra various, multi-client community — and a cautious governance path for delicate protocol modifications.
Backside line: builders are on schedule to ship Part 1 options in 2026 and to pursue Peras in 2027, however group testing, node range efforts and governance actions will decide the ultimate mainnet dates.
