Cardano Moves Plutus Cost Model Update to PreProd as eUTXO Scaling Debate Returns

Cardano Plutus Cost Model Update Reaches PreProd

Cardano’s Plutus Cost Model parameter update was enacted on the PreProd test network on May 16, giving developers a live environment to test existing scripts before the change moves further toward mainnet. Intersect said developers are strongly encouraged to review their current settings ahead of progression, especially where applications rely on Plutus execution budgets.

The update increases CPU cost model parameters for selected Plutus primitives. The affected operations include equalsByteString across Plutus V1, V2 and V3, along with several Plutus V3 integer operations, including divideInteger, modInteger, quotientInteger and remainderInteger. For users, this may not appear as a visible product change. For developers, it changes the execution environment that smart contracts depend on.

Plutus cost models define how computational work is priced when scripts run on Cardano. If a script is already close to its CPU budget, a cost increase can affect whether that script still fits within execution limits. That makes PreProd testing essential for DeFi protocols, NFT platforms, identity applications, governance tools and any production system using Plutus scripts.

Why the Plutus Update Matters for Cardano Developers

The Plutus Cost Model update is part of the broader Van Rossem upgrade path. Intersect’s May 8 update described continued preparation around node, infrastructure and ecosystem readiness, and noted that a Plutus cost model protocol parameter update governance action had been submitted on PreProd.

The point is not that Cardano becomes faster because one parameter update reached a test network. The more precise point is that Cardano is adjusting the rules that define how smart contract execution is measured. That matters because Cardano’s developer environment depends heavily on predictable costs, reliable transaction behavior and clear execution boundaries.

This is infrastructure work, not marketing material. Cost model changes sit below the surface of the user experience, but they shape whether applications remain stable when protocol parameters evolve. Teams that maintain smart contracts now have a direct reason to test, measure and adjust before the same assumptions are carried into mainnet conditions.

The risk is practical. Older contracts, tightly optimized scripts or applications already operating near execution limits may need review. That does not make the update negative. It makes the testing window valuable.

Charles Hoskinson’s eUTXO Response Adds the Bigger Context

The same day, Charles Hoskinson responded to an X post claiming that an AI analysis had concluded Cardano could not scale because of its UTXO architecture. Hoskinson dismissed the claim sharply, writing: “Dunning Kruger AI edition. ‘AI Told me that UTXO cannot scale.’”

That exchange should stay secondary to the technical news, but it explains why the Plutus update matters beyond one parameter change. Cardano is still often judged through assumptions built around account based blockchains, even though its architecture follows a different model. Cardano Docs explains that Cardano uses an Extended UTXO model, extending Bitcoin’s UTXO approach with support for multi assets and smart contracts.

The misunderstanding is not only about terminology. In an account based system, developers and analysts often think in terms of shared state. In Cardano’s eUTXO model, application design depends on different assumptions around validation, transaction construction and parallel execution. That makes shallow comparisons misleading, especially when they reduce Cardano’s scaling model to a generic AI summary instead of examining how real applications are built.

The Plutus Cost Model update is Cardano’s more useful answer to that debate. It gives developers a concrete test environment, specific primitives to review and a clear reason to check whether their applications remain within execution limits. If eUTXO criticism is going to be taken seriously, it has to meet Cardano where the architecture is actually tested: in scripts, budgets, transaction design and production readiness, not in simplified claims about what UTXO can or cannot do.