CAP-12 Proposes Cardano Constitution Changes for Dijkstra

The amendment would establish governance rules for new protocol parameters, while Node 11.2 is being prepared to test Dijkstra features, including a new block format and Plutus V4 context.

By SongMarketCap

Cardano News - CAP-12 Proposes Cardano Constitution Changes for Dijkstra

CAP-12, a proposed amendment covering Dijkstra protocol parameters, is open for public consultation. Intersect’s October 2 update outlined the proposal alongside preparations for Node 11.2, with a pre-release expected soon for wallet and infrastructure teams.

Dijkstra Parameters in the Cardano Constitution

Cardano’s Constitution permits Parameter Update actions to change only settings explicitly listed in Appendix I. Without the amendment, Dijkstra’s new parameters would remain fixed at their initial values despite being technically adjustable.

CAP-12 covers reference-script protection, Ouroboros Leios, Ouroboros Peras, and stake pool economics. Its scope includes Leios capacity and timing settings, minimum pool margin, and maximum pledge leverage.

For each parameter, the proposal describes its function, assigns its voting group, and defines limits on future changes. The group determines the approval threshold for DReps, representatives to whom ADA holders delegate voting power. Security-critical parameters also require stake pool operator approval.

An updated Guardrails Script would automatically enforce constraints that can be checked on-chain. The amendment adds provisions without changing or removing existing constitutional text.

Node 11.2 Prepares Dijkstra Integration Testing

Release sequencing for Node 11.2 is underway, according to Intersect. The planned pre-release will contain most of the Dijkstra feature set, including the new block format and Plutus V4 context, which defines information available to smart contract scripts.

Wallet and tooling teams will be able to test integrations and assess changes to protocol behavior, APIs, and functionality. The release will exclude Leios and will not be ready to activate the hard fork.

Hardware wallet providers also have preparation work involving cryptographic keys and stake pool registration requirements for Leios. Those requirements extend beyond the contents of the upcoming test release.

Pending Guardrails and Later Activation

The proposed guardrails link changes to Leios capacity with benchmarking and simulations demonstrating that nodes can process and distribute data within the required time.

CAP-12 also distinguishes between activation stages. Maximum pledge leverage, a pool parameter linked to operators’ own ADA pledges, would initially have no configured value. Enabling it would require a subsequent governance action. Peras and minimum pool margin are intended for a later hard fork within the Dijkstra era.

The proposal remains under consultation, with an initial editor review expected. Numerical bounds for Endorser Block capacity and Leios timing are among the values still marked “PENDING” in the draft.