Cardano Plutus Cost Model Update Moves to Mainnet Tonight Ahead of van Rossem Hard Fork

Cardano’s Plutus Cost Model parameter update is scheduled to take effect on mainnet on June 18, 2026, at 21:45 UTC, following ratification through on-chain governance. The action was ratified on June 13 with 68.57% DRep approval and 5 of 7 Constitutional Committee votes.

The update applies to how Cardano measures the computational cost of Plutus smart contract execution. For developers and dApp teams, the main impact is practical testing, fee estimation, transaction balancing and script validation under the updated mainnet parameters.

Cardano Mainnet Prepares for Plutus Cost Model Enactment

The Plutus Cost Model defines how Cardano calculates the execution cost of Plutus smart contract scripts. It assigns execution values for CPU and memory use, which are then used when calculating transaction fees connected to script execution.

The mainnet Plutus Cost Model action was submitted on May 26, 2026, and later ratified through Cardano’s on-chain governance process. Its scheduled enactment on June 18 applies updated parameters to mainnet before the broader van Rossem hard fork process reaches its own enactment stage.

Intersect has described the mainnet upgrade path as two separate governance actions. The first is the Plutus Cost Model parameter update, while the second is the hard fork initiation action for Protocol Version 11.

The governance action is titled “Update Plutus Cost Models” and is classified as a Protocol Parameter Change. Once enacted, the updated cost model settings become part of the active protocol parameters used by applications, wallets and infrastructure that build and validate Plutus transactions.

What Changes for Plutus Scripts and dApp Teams

According to Intersect, the Plutus Cost Model update contains two groups of changes that take effect at different stages. The first group includes increases in the cost model for some existing primitives. These changes take effect immediately after the parameter update is enacted.

For dApp teams, wallet providers, transaction builders and infrastructure providers, the update changes the environment used to calculate Plutus execution costs. Applications that depend on smart contract scripts may need to check fee calculation, transaction balancing, script evaluation and any local assumptions built into their tooling.

In practical terms, this affects how a transaction is prepared before it is submitted to the network. If a dApp uses Plutus scripts, its tooling must estimate execution costs correctly so the transaction can be built, balanced and submitted without unexpected failures.

Cardano’s Plutus design allows script execution costs to be evaluated before a transaction is submitted. That makes accurate cost model settings important for teams building applications that rely on smart contracts, especially DeFi protocols, NFT infrastructure, wallets and other transaction-heavy applications.

The update does not make newly introduced Plutus primitives usable immediately. Intersect states that those primitives become available only after the van Rossem hard fork itself. Tonight’s scheduled parameter update places the related cost settings in position so they can be used after Protocol Version 11 is enacted.

van Rossem Hard Fork Remains on a Separate Governance Track

The van Rossem hard fork is expected to introduce Protocol Version 11 and expand Plutus with additional built-in functions. Intersect’s documentation references new technical elements connected to CIP-109, CIP-132, CIP-133, CIP-138 and CIP-153.

The Plutus Cost Model update is part of that path, but it is not the final hard fork event. Its role is to update current execution cost parameters and prepare cost settings for primitives that will become available only after Protocol Version 11 is enacted.

Preview and Preprod testing preceded the mainnet step. On Preprod, the Plutus Cost Model update was enacted before the hard fork, giving dApp teams and developers time to test against the cost changes before mainnet progression.

After tonight’s scheduled enactment, the active focus for builders shifts from governance status to mainnet verification. The relevant areas include Plutus scripts, fee estimation, transaction builders, wallet integrations and application flows that depend on script execution costs.

The next phase of the van Rossem process remains tied to the separate hard fork initiation governance action. That process involves Constitutional Committee members, DReps and SPOs, with Protocol Version 11 dependent on its own approval and enactment path. For Plutus developers, tonight’s parameter update is the point where updated cost assumptions move from testing environments into the live mainnet execution layer.