Exchange Ranking
Top Exchanges
24h Volume Ranking
Popularity Ranking
Exchange BTC Balance
Proof of Reserves
Decentralized Exchanges
Funding Rate
Funding Heatmap
Liquidation Data
Max Pain
Long/Short Ratio
Whale L/S Ratio
Binance/Okex/Huobi L/S
Bitfinex Margin L/S
ETF Tracker
Solana ETF
XRP ETF
Hong Kong ETF
Bitcoin Treasuries
Crypto Reversal
Ethereum Reserves
HyperLiquid Wallet Analysis
Hyperliquid Whale Watch
Large Transactions
On-chain Movement
Bitcoin ROI
Stablecoin Market Cap
Options Analysis
News
Articles
Economic Calendar
Features
Wallet
Contract Calculator
Security
Collections
Watchlist
Following
ADA Intersect reported that preparations for Cardano's Dijkstra era hard fork progressed as planned, with no adjustments to the established scope and milestone dates. According to the latest update, all major components and goals are progressing steadily as planned.
Dijkstra Hard Fork Phase and Technology Upgrade
The Dijkstra Era will be introduced through two main phases. The first phase will deliver nested transactions and linear Leios to the Cardano main network by the end of 2026, aiming to gradually roll out key functions. The second phase will enable Peras, which is planned to be activated in an intra-era hard fork in the second quarter of 2027.
Dijkstra will bring a series of major upgrades to Cardano, particularly notable among which is Ouroboros Leios. This upgrade will allow you to set new, updatable protocol parameters. The Cardano Constitution stipulates that only parameters clearly listed in its guardrails can be changed through governance.
To comply with constitutional requirements, stakeholders plan to introduce all necessary Dijkstra parameters at once through a unified proposal. This approach aims to maintain consistency and clarity in the protocol update process and avoid fragmentation due to multiple proposals.
Node diversity: Amaru's progress and goals
The continued development of Cardano alternative node software has also been highlighted as an important factor in enhancing network resilience. Increased node diversity helps reduce reliance on a single implementation version and provides additional security and flexibility to the ecosystem.
Amaru, a fully open source implementation of Cardano nodes built using the Rust programming language, has demonstrated important progress. The development team confirmed that Amaru now has relay capabilities and has successfully verified and synchronized to the latest network status. The team has set a goal of achieving main network block production by November 2026, which will further expand the diversity of nodes available to Cardano users and operators.
Small Dictionary:
Amaru is a Cardano node implementation written in Rust that aims to provide a modular and robust alternative to Cardano's existing Haskell-based nodes. Nodes with relay capabilities can participate in spreading blocks and transactions, while block production capabilities allow them to directly participate in the consensus process.
Amaru's design priorities include interoperability, modular architecture and reduced hardware requirements, aiming to provide better options for developers and equity pool operators in the Cardano network.
Constitution Updates and Community Governance
Before the arrival of the Dijkstra era, Cardano is preparing a technical update to its constitution to ensure that all upcoming features and parameters can be handled by the network governance structure from the beginning of release.
Intersect stated that amendments related to Dijkstra now follow a simplified path for community discussion, proposal submission and formal promulgation. The process leverages the newly introduced Constitution Amendment Portal (CAP), which promotes transparent dialogue and voting and is supported by Citizens 'Committees.
The latest report highlights that as Cardano approaches these important technical and procedural milestones, governance processes and community engagement remain a focus.
Cardano's Constitution enforces strict guardrails, stipulating that parameters of the agreement that are not explicitly listed cannot be changed through governance. As the era of Dijkstra approaches, all relevant parameters will be introduced in one go through a coordinated proposal.
