Cardano Parameter Update No Work After SPO Support No Reach Requirement

The action wey dem title “Reduce minPoolCost to 75 ADA and increase Plutus Memory Limits (Part 2),” expire on September 1. DRep support reach 68.57%, wey pass the required 67% threshold, but SPO support end for 34.5%, wey no reach the required 51%.

Cardano Parameter Update Miss SPO Threshold

The governance action join two separate protocol parameter changes together.

The first propose to reduce minPoolCost from 170 ADA to 75 ADA. The parameter na the minimum fixed cost wey stake pool fit remove from rewards before dem share the remaining rewards give delegators.

The second propose to increase Plutus execution memory limits. Maximum memory per transaction go rise from 16.5 million to 17.5 million units, while maximum memory per block go increase from 72 million to 77.5 million units.

Intersect describe the action as combination of two independent protocol parameter changes wey dem don recommend before.

The Constitutional Committee record five votes in favor, no votes against and two members no vote. The DRep threshold self reach. Na only SPO approval be the required threshold wey the action no meet before e expire.

Plutus Memory Change Need SPO Approval

The proposed minPoolCost reduction on its own no go require stake pool operator vote under Cardano current governance framework.

minPoolCost belong to the economic group of protocol parameters. The SPO requirement trigger because the same governance action also include change to maxBlockExecutionUnits[memory], wey dem classify among Cardano security relevant critical parameters.

When one governance action join parameters wey get different approval requirements, all the thresholds wey attach to those groups must dey satisfied. The Plutus block memory change therefore make SPO approval necessary for the whole action.

The result leave the action above the DRep threshold but below the required SPO threshold.

Intersect don already report limited SPO participation during the voting period. One late August update show SPO support at 26.11% before the final figure rise to 34.5%.

No official analysis don put the result for only one cause. Some governance participants criticize the decision to combine unrelated parameter changes inside one action, while public SPO commentary also raise broader questions around stake pool economics.

CAP #10 Broaden the Stake Pool Governance Debate

After the action expire, the Constitutional Amendment Portal list CAP #10 with the title “Require SPO Approval for Changes to Stake Pool Economic Parameters.”

The proposal currently mark In Consultation, wey mean say e dey for off-chain public discussion stage. E no dey change Cardano ledger rules or existing governance thresholds for now.

The title propose say SPO approval suppose dey required for changes wey involve stake pool economic parameters. Under the current framework, economic parameters no dey independently require SPO vote unless dem include am for action wey also contain parameters wey SPO approval dey mandatory.

The full CAP #10 text, the authors, the exact parameters e go cover and any proposed voting threshold no fit confirm from the publicly accessible primary document.

Public discussion after the expired action also include proposals to submit future minPoolCost and Plutus parameter changes separately. That one go allow each change to proceed under the governance thresholds wey match im own parameter classification.

The failed action therefore produce one concrete governance question beyond the original parameter changes: whether future decisions wey alter stake pool economics suppose require direct SPO approval by constitutional design, instead of only when another critical parameter happen to carry SPOs enter the vote.