Mesmo targets the gaps between Cardano SDKs
The Cardano Foundation has introduced Mesmo, a native library designed to give developers in Python, Go, Rust and JavaScript access to Cardano functionality that may not yet be available in their preferred software development kit. Rather than replacing existing libraries, Mesmo is designed to work alongside them.
The project addresses a practical issue in Cardano’s multilingual developer ecosystem. Teams currently use libraries such as pycardano, MeshJS, Lucid Evolution, pallas and Apollo, while Cardano Client Lib provides a broader Java-based feature set. Mesmo aims to make selected capabilities from that underlying implementation available across four additional programming environments.
The approach is particularly relevant when new Cardano protocol functionality arrives. Governance operations, DRep functions, committee operations and other features introduced during the Conway era can require individual SDK maintainers to implement and release corresponding support. Mesmo provides another route when a developer’s main library does not yet expose a particular capability.
At the center of Mesmo is Cardano Client Lib, which is compiled into a native shared library using GraalVM Native Image. The resulting library uses a C application programming interface, allowing wrappers in other programming languages to access the underlying functionality without requiring a Java Virtual Machine at runtime.
The library is designed to remain stateless. It does not operate as a Cardano node, maintain chain synchronization or handle node protocols. Instead, chain information required for tasks such as UTXO selection and protocol-parameter retrieval can be supplied through a ChainDataProvider interface, allowing developers to connect existing infrastructure.
Native transaction and governance tooling across four languages
Mesmo exposes functionality covering account management, transaction construction, key derivation, addresses, native scripts and Plutus-related operations. It also supports Cardano governance capabilities, including DRep registration and delegation, voting and governance actions, alongside staking and stake-pool operations.
Transaction construction is organized around the TxPlan model, which allows developers to describe intended actions while the library handles tasks such as input selection, fee calculation and change. The same underlying implementation can therefore be accessed through the different language wrappers instead of maintaining separate transaction-building logic in each ecosystem.
The project also includes an embedded Scalus evaluator for offline Plutus execution-unit costing, while developers can use external evaluators where required. The architecture keeps data providers and transaction submission separate, meaning applications can continue using their existing HTTP infrastructure for communicating with Cardano services.
A major part of Mesmo’s pitch is testing. According to the project documentation, supported transaction types are built and submitted to a Cardano devnet as part of continuous integration testing. This includes payments, staking, governance operations, pool operations, native scripts and Plutus transactions, providing an on-chain validation step beyond ordinary unit tests.
The four wrappers are intended to remain thin layers over the same native core. This reduces the possibility of different languages implementing the underlying Cardano operations differently, while still giving developers interfaces suited to their respective programming environments.
Python, Go, Rust and JavaScript developers can therefore approach the same Cardano functionality through their existing workflows. The JavaScript implementation currently targets the Bun runtime rather than Node.js, while native libraries are available for several Linux, macOS and Windows configurations.
Related: Cardano Turns Nine With 123.9 Million Transactions and 36,322 Governance Votes
Mesmo is still a pre-release project, which is an important distinction for developers considering production use. The project currently tracks a pre-release version of Cardano Client Lib, meaning interfaces and behavior can change before a stable release. The devnet-based testing provides an additional validation layer, but it does not remove the normal risks associated with early-stage software.
The library also comes with trade-offs. The native dependency adds roughly 60 MB to an application, JavaScript teams committed to Node.js face a current runtime limitation, and developers remain responsible for choosing appropriate data providers and submitting transactions through their own infrastructure.
The roadmap includes additional chain-data providers, a code-first QuickTx builder and a WebAssembly target. The planned WebAssembly support could eventually broaden Mesmo beyond native library environments, including browser-based applications and server environments capable of running WebAssembly.
For Cardano, the significance of Mesmo is less about adding another SDK and more about reducing the distance between protocol development and application development. As new features reach the blockchain, developers using different programming languages have another way to access functionality without immediately abandoning an established toolkit.
The Foundation has already identified developer tooling as part of its broader ecosystem work, with its August activity report highlighting Mesmo alongside other Java and developer-infrastructure projects. If the library can maintain compatibility with Cardano’s evolving protocol while keeping its wrappers stable, it could become a practical bridge between the network’s core capabilities and the diverse software stacks used by Cardano developers.















