Cardano’s DijkstraNet Reopens for Public Testing
Stake pool operators can join the restarted network ahead of its planned transition to protocol version 12. Intersect also confirmed CIP-23’s inclusion in Dijkstra’s scope, without establishing an immediate change to pool fees.
By SongMarketCap
Intersect Invites Operators to Join DijkstraNet
Cardano’s DijkstraNet became publicly available following an October 21 restart, according to Intersect’s Upgrade Bulletin #39, published October 22.
At the time of the bulletin, the network was running node 11.1.3 under protocol version 11, in the Conway era. Intersect invited stake pool operators to join ahead of the node 11.2 pre-release.
That release was intended to support a test-network hard fork to protocol version 12, introducing the Dijkstra ledger era.
The public network gives pool operators, wallet providers, and infrastructure teams an environment for checking compatibility before mainnet deployment. The bulletin did not announce a mainnet activation date.
CIP-23 Introduces a Separate Pool Margin Parameter
Intersect also confirmed that CIP-23, known as Fair Min Fees, was included in the Dijkstra hard fork scope.
The proposal introduces minPoolMargin, a protocol parameter setting a lower bound on a stake pool’s percentage fee. It operates independently of minPoolCost, the existing minimum fixed pool fee, which the proposal does not itself remove or reduce.
CIP-23 recommends introducing the margin parameter at zero to avoid disrupting existing pool configurations. A higher value would require a subsequent governance decision.
The official Dijkstra overview distinguishes introducing the parameter from activating its fee rule. Activation can occur in the first phase if implementation and governance are ready, or through a later hard fork within the Dijkstra era.
Delegators therefore should not interpret inclusion in the upgrade’s scope as an approved increase in pool fees.
[NEWSBREAK]
Leios Testing Continues on a Separate Network
The bulletin described node 11.2 as covering Dijkstra features without Leios. Leios testing proceeds separately on MusashiNet, allowing teams to work on integrations before the broader release is ready.
This separation concerns the testing process. Linear Leios remains part of the wider Dijkstra upgrade plan.
Mainnet deployment also requires a hard fork governance action involving DReps, stake pool operators, and the Constitutional Committee. Opening DijkstraNet begins a broader opportunity for testing without completing those approval steps.
For participating operators, the immediate work is to connect their infrastructure, test compatibility, and report problems. The next transition identified in the bulletin depends on the node 11.2 pre-release and a governance action moving the test network to protocol version 12.