Cardano Don Approve Plutus Cost Model Update, Dem Go Start Am June 18

Cardano don ratify the governance action for the Mainnet Plutus Cost Model update on June 13, 2026. According to Intersect MBO, enactment dem schedule am for June 18 around 21:45 UTC. The protocol parameter change go update Plutus cost models for V1, V2 and V3, the parameter sets wey dem dey use calculate execution units for smart contract transactions for Cardano.

Cardano Governance Approve the Update Plutus Cost Models Action

The governance action, wey dem title “Update Plutus Cost Models,” na protocol parameter change for Cardano mainnet. For CardanoScan, the action show as ratified under governance action ID gov_action1eqhnsdyf3exhp5mqt7sdjtl7xy69wqg8tvg854psns2jt72cra3qqrcnr8r.

CardanoScan show five Constitutional Committee votes wey support the action, no vote against and no abstention. The DRep vote get 3.94 billion stake wey support am, equal to 68.61 percent support. SPOs no qualify to vote for this kind parameter update action, and the explorer data show this one too.

Ratification mean say the governance action don collect the required approval through Cardano on-chain governance process. Enactment na the separate step wey dem take apply the approved parameter change to the network. After enactment, the updated cost models go become part of the mainnet parameters wey tools dey use estimate execution budgets, fees and Plutus script behavior.

Plutus V1, V2 and V3 Cost Models Don Get New On-Chain Values

The Plutus Cost Model determine the part of transaction fee wey cover Plutus script execution. E assign execution units through CPU and memory components, and na these ones dem take calculate fees for transactions wey use smart contracts.

Plutus V1 refer to the original version of Cardano smart contract scripting environment wey dem introduce with the Alonzo era. Plutus V2 expand scripting capabilities through the Vasil upgrade, including features wey enable more efficient dApp designs. Plutus V3 na newer iteration wey relate to the Conway era and later upgrades, with expanded set of built-in functions and cost model parameters.

The on-chain governance action dey update the full cost model arrays for plutusV1, plutusV2 and plutusV3. The announced materials highlight changes wey relate to equalsByteString across V1, V2 and V3, plus the integer operations divideInteger, modInteger, quotientInteger and remainderInteger for V3. One public technical clarification for the Intersect thread still talk say the changes no limit to CPU values and say additional V1 and V2 changes dey, including memory costs.

For developers, the authoritative source na the full set of new values wey dem record for the on-chain governance action and wey CardanoScan, Cexplorer, AdaStat and related tools dey display. No official table wey compare all previous and new values come out for the announcement, so teams wey need full technical comparison must compare the new on-chain arrays with the previously active ledger cost model definitions.

Developers Need to Retest ExUnits, Fees and Script Budgets

Intersect don ask developers and dApp teams make dem test their setups for Preview and Preprod before enactment. The reminder apply to DeFi protocols, NFT infrastructure, wallet integrations, indexers, transaction builders and backend services wey dey calculate fees, CPU, memory and collateral values before dem submit transactions to mainnet.

The practical test for teams na to run their scripts again and re-estimate script costs using current dApp code, transaction builders and cost estimation libraries. The goal na to confirm say scripts still dey execute within the expected ExUnits limits and say fee and collateral calculations still align with the new mainnet cost model parameters.

If wallet, dApp or transaction builder dey use hardcoded or outdated cost model values, e fit calculate wrong execution budget. After enactment, that one fit cause failed transaction execution if the budget too low, or make fee estimates too high if the tool dey calculate from old or inaccurate assumptions.

The Plutus Cost Model update na separate protocol parameter change action, e different from the Van Rossem hard fork governance process. E still be part of the same technical readiness period for Protocol Version 11, as wallets, infrastructure providers, dApps and node operators dey prepare for ledger and Plutus changes. On June 18, the updated cost models for existing parameters go apply to mainnet, while newly introduced Plutus primitives go only become active after hard fork activation.