Cardano Wan Update Constitution To Make Leios Parameters Fit Get Governance Before Dijkstra

Input Output Group don outline one plan to update the Cardano Constitution before the Dijkstra era, to focus on one practical governance matter wey new protocol features cause.

Dijkstra dey expected to introduce Ouroboros Leios and nested transactions. The two features go bring new updatable protocol parameters, but Cardano governance fit only adjust parameters wey dem list clearly inside the Constitution Guardrails. If dem no update am before the hard fork, those new settings fit turn active for on-chain but governance no go fit adjust am.

Cardano Constitution Update Target Dijkstra Readiness

Cardano Constitution dey put formal limits for protocol governance by defining which parameters dem fit change and the ranges wey dem fit change am. This structure dey reduce open ended control over the protocol, but e still require make new hard fork parameters enter the list before people fit manage dem after activation.

The proposed update go add the Dijkstra related parameters and their Guardrail ranges inside the Constitution. IOG talk say the change na only for that technical purpose and e no dey alter the Constitution tenets, the roles of DReps, stake pool operators or the Constitutional Committee, voting thresholds or existing rights.

That clear difference keep the proposal focused on hard fork readiness, no be broad constitutional reform. The update no be redesign of Cardano governance, na procedural step wey need happen before the network enter new protocol phase.

For ADA holders wey DReps dey represent, the proposal dey move Dijkstra preparation enter the formal governance process before Leios and nested transaction parameters become part of the live network.

Leios and Nested Transactions Need Defined Guardrails

Ouroboros Leios na Cardano planned scaling upgrade for higher throughput and more responsive transaction processing. The design depend on parameters wey dem fit tune as network conditions change, and that one mean governance access to those settings dey part of the operating model.

The Constitution update no go give governance unlimited control over those parameters. Instead, the Guardrails go define the permitted range for future adjustments, make the network fit adapt without removing the constitutional limits around protocol changes.

Nested transactions add another technical layer for the Dijkstra upgrade path. Dem dey expected to expand how transactions fit take structure and how people fit use dem inside Cardano protocol. If those features introduce new adjustable parameters, those settings too need make the Constitution recognize dem before the hard fork take effect.

The result na sequencing requirement: the protocol fit introduce new capabilities through Dijkstra, but governance need defined authority over the related parameters before those capabilities activate.

DReps and Constitutional Committee Go Review One Proposal

IOG talk say the plan na to prepare one Constitution proposal wey cover all Dijkstra related parameters, instead make dem split the update into several separate actions. This approach go give DReps single technical package to assess before voting.

The process go start with finalizing the Dijkstra scope and identifying the exact parameters wey dey involved. Intersect Parameter Committee dey expected to define the Guardrails for each parameter, while the Plutus team go prepare the updated Guardrails Script wey go follow the Constitution change.

DReps go vote for ratification, while the Constitutional Committee go confirm whether the action dey constitutional. IOG talk say the target na to submit the governance action no later than epoch 655, wey go begin on September 11, 2026, at 21:44 UTC.

The proposal dey put Cardano next hard fork for defined governance path before the new protocol logic activate. Dijkstra fit bring Leios and nested transactions enter the technical roadmap, but na the Constitution update go determine whether the parameters behind those features go enter mainnet with clear limits, review and adjustable control from day one. For ADA governance, the decision no be only about adding new settings, e still dey about defining the range of control before those settings become part of the live protocol.