Cardano Plutus 1.68.0.0 Brings Plutus V4 Into the Development Stack

Cardano’s smart contract stack has moved closer to the Dijkstra era with the release of Plutus 1.68.0.0. The update introduces Plutus V4 ledger API types, expands on-chain asset handling and simplifies the process of starting new Plinth projects.

The release does not activate Plutus V4 on Cardano mainnet, but it brings parts of the next execution environment into the current development toolchain.

Plutus V4 Types Enter the Current Toolchain

Plutus provides the execution language and tooling used by Cardano smart contracts. Its ledger API exposes transaction and blockchain data that scripts can inspect when validating transactions.

Version 1.68.0.0 adds Plutus V4 and the associated dijkstraPV ledger API support. The release also adds V4 to CIP-57 contract blueprints, allowing scripts to be identified as version v4.

The Plutus team cautions that V4 is still under development and that the new ledger API types may change before Dijkstra.

Development is also continuing on direct pattern matching over Data. A case expression can now dispatch directly on the constructor tag of a Data.Constr value. Combined with the recently added dropList functionality, this reduces overhead for script logic that works with structured on-chain data.

New Builtins Improve Asset Validation

Plutus 1.68.0.0 also introduces the assetCount builtin from CIP-0168 together with its cost model.

The function returns the number of distinct policy ID and token name pairs contained in a value. This gives smart contracts a direct way to verify how many different assets are present instead of manually traversing the complete value structure.

The functionality is relevant to Cardano’s multi-asset model. A DeFi contract, for example, may need to verify that a UTxO contains ADA, DJED and a specific set of protocol tokens while rejecting unexpected assets that could interfere with validation or increase later transaction costs.

The release also adds benchmarked costing for multiIndexArray, a builtin designed to retrieve several array elements in one operation. This reduces repetitive lookup logic when scripts need multiple positions from the same array.

These additions move functionality previously described through Cardano Improvement Proposals further into released Plutus code.

Plinth Setup Moves to a One-Command Workflow

The same development cycle also simplifies onboarding for Plinth, the Haskell framework used to build Plutus smart contracts.

The updated plinth-template includes an installation workflow that can create a new project with a single command while handling the required development tooling and project structure.

This gives the release two separate development effects. Plutus 1.68.0.0 exposes more of the execution environment being prepared for Dijkstra, while the Plinth changes reduce the setup required for developers to begin working with it.

Plutus V4 is still being defined, but developers now have a broader implementation surface to test against. Ledger API types, new builtins and updated tooling are moving the next Plutus generation from specification work into usable development releases before the Dijkstra ledger era reaches activation.