The Intersect organization, established to develop the Cardano blockchain ecosystem, has published a detailed description of the Dijkstra update, which will be deployed in two stages. In the first stage, the developers plan to focus on the Ouroboros Linear Leios (CIP-164) feature, which is designed to increase the network’s throughput when processing transactions through additional confirmation blocks. The first phase also includes a number of important protocol changes: nested transactions (CIP-118), security scripts (CIP-112), extended account addresses (CIP-159), and a simplified method for withdrawing staking rewards (CIP-181). These changes are aimed at enhancing the functionality and usability of the network. The first phase is planned to be completed by the end of this year; however, before being implemented on the main network, the changes will be tested on the public Musashi Dojo testnet, which was launched on June 23.

The second phase of the update is scheduled for the second quarter of 2027 and includes the deployment of Ouroboros Peras (CIP-140). This update should further speed up transaction processing on the blockchain due to the introduction of an additional voting layer in the staking pool. The creators of Cardano plan to release a compatible node for testnet operators, which will allow staking pool operators to prepare the infrastructure in advance for future hard forks. The developers will then carry out a preliminary hard fork, opening the first testing window for two weeks, and then move Peras to the pre‑production network for the second stage of testing, which will last another one to two weeks. Additional tests will give the team a chance to identify and fix problems before launching on the main network. Final activation will require the approval of delegated representatives, pool operators, and the Constitutional Committee. The exact launch date has not yet been announced.

It should be recalled that in July, the Cardano team already activated the Van Rossem hard fork, the purpose of which was to reduce the cost of executing Plutus smart contracts and to prepare the blockchain for future large‑scale changes.