Cardano’s New Smart Contract Library Exceeds Its Original Target

Cardano's ContractsLibrary initiative has prepared six reusable smart contracts, exceeding its original target of five. Robertino Martinez, who leads the Developer Experience initiative at AlwaysTrue, revealed the progress during the X Space discussion Decentralizing Cardano’s Core Development.

The library aims to give developers ready-to-integrate smart contract components instead of requiring them to build common functionality from scratch. Inspired by OpenZeppelin’s approach in the Ethereum ecosystem, the project combines on-chain code, transaction-building tools, technical specifications, and formal verification.

The six contracts have reached the final code and specification review stage. Martinez emphasized that they have not completed security audits and should not yet be deployed on Cardano mainnet.

Six Contracts Move Toward Public Testing

ContractsLibrary was originally expected to deliver five reusable smart contracts. According to Martinez, the development team prepared six and began final quality checks ahead of broader community testing.

The initiative focuses on complete, application-oriented components rather than isolated programming functions. Developers are intended to be able to configure existing contracts, adapt their source code, or combine components to meet different application requirements.

The library draws on development patterns already established within Cardano, including work by Anastasia Labs.

Martinez also confirmed that the high-assurance team had started formal verification work. Its initial focus is on properties shared across the contracts, followed by the verification of individual implementations.

The distinction between completed development work and production readiness remains important. Six prepared contracts do not mean six audited or formally verified contracts are already available for unrestricted use.

An OpenZeppelin-Inspired Development Stack for Cardano

OpenZeppelin has become a widely used resource for reusable smart contract components in Ethereum and other EVM ecosystems. ContractsLibrary aims to provide a comparable development resource adapted to Cardano’s extended UTxO architecture.

Each implementation is designed to combine several connected elements.

The on-chain component uses Aiken to define the rules enforced by Cardano’s ledger. Off-chain transaction builders, including support for MeshJS and Tx3, help applications construct the transactions required to interact with those validators.

Technical specifications describe the intended behavior of each contract, while testing and formal verification provide additional ways to evaluate whether implementations satisfy defined requirements.

The project also uses Lean 4 for machine-checked proofs of selected contract properties.

This integrated structure addresses a practical challenge in Cardano development: building a decentralized application often requires coordinating smart contract validation with off-chain transaction construction.

By providing connected components, ContractsLibrary aims to reduce repetitive development work and make common contract patterns easier to integrate into new applications.

[NEWSBREAK]

Security Reviews Remain the Final Requirement

ContractsLibrary is part of the broader Developer Experience initiative, which has transferred from Input Output to AlwaysTrue under Martinez’s continued leadership.

The initiative includes other tools such as cardano-init, which helps developers generate connected Cardano development environments.

For ContractsLibrary, the immediate priorities are completing code quality checks, making the implementations accessible for testing, and continuing formal verification.

Martinez advised developers to treat the initial release as a testing opportunity rather than a production-ready library. He also identified the approaching Dijkstra hard fork as an additional reason for caution while Cardano’s development tools adapt to upcoming protocol changes.

The project distinguishes contracts prepared for security audits from those that have completed the required reviews and reached stable status.

Its public repository provides code and development documentation, but the available materials do not establish that all six contracts have been released as stable implementations.

Martinez’s update therefore establishes a concrete development milestone: the team has prepared one more contract than originally planned. Public testing, individual verification, and the required security reviews remain separate steps before those implementations can be treated as production-ready components.