On October 8, 2026, Input Output Global (IOG) announced that Cardano is now supported by the Open Wallet Standard (OWS), starting with version 1.4.3. Read the original announcement: Open Wallet Standard adds Cardano support.
This development deserves attention as AI agents become increasingly relevant to blockchain applications.
- How can AI agents interact with wallets while operating within clearly defined permissions?
- What does this mean for Cardano?
To explore these questions, let’s look at how the Open Wallet Standard (OWS) works, how its signing policies help control agent access, and what this integration could enable developers to build on Cardano.
1. Why does this matter?
Imagine an AI agent interacting with a Cardano wallet. It could check the wallet’s balance, prepare a transaction, or request a signature to authorize it.
But how much access should the agent have? Should it be allowed to sign any transaction it prepares, or should its signing authority be limited to specific, predefined permissions?
That question is where OWS becomes interesting.
OWS is an open-source standard for wallet management and signing across supported blockchains. It provides a common interface for applications and AI agents, with access keys and policies that can restrict which signing requests are permitted.
Instead of treating every agent as fully trusted, developers can assign different access keys and permissions to different agents.
Explore the official OWS website and the OWS source-code repository.
2. OWS is not only about Cardano
Cardano is the latest addition to this story, not the whole story.
OWS supports multiple blockchain ecosystems, including Ethereum and other EVM networks, Solana, Bitcoin, Cosmos, Tron, TON, Sui, NEAR, and Filecoin.³
Source: OWS-Supported Chains documentation.
Why does this matter?
Consider a developer building an AI agent that needs to work across several blockchains. Without a common interface, each chain may require its own wallet integration, signing method, and key derivation rules.
OWS aims to provide a common approach to wallet management and signing while accommodating the specific requirements of each supported blockchain.
For Cardano developers, this means they can explore this approach within the Cardano ecosystem.
One distinction deserves attention: a common interface does not mean a common implementation. Each blockchain retains its own transaction formats, cryptographic requirements, and signing processes.
3.How Does OWS Signing Work?
Imagine an AI agent requesting a signature for a Cardano transaction through OWS.
Here is how the process works:
Simplified illustration based on the official OWS architecture and policy engine documentation.
-
Signing request: The agent submits a request using its assigned access key.
-
Policy checks: OWS evaluates the policies attached to that key before accessing the protected key material.
-
Decision: If the request meets the policies, OWS proceeds with signing; otherwise, it is rejected.
For example, a custom policy could allow a 3 ADA transaction and reject a 7 ADA transaction under a 5 ADA per-transaction limit. This limit is an example, not a built-in rule.
Security matters: Policies apply to agent access keys, not automatically to the owner’s direct access. Never give an agent the owner’s wallet passphrase.
Finally, signing does not necessarily mean the transaction has been submitted to or confirmed on-chain.
4. What is specific to Cardano?
A common wallet interface must still account for each blockchain’s specific requirements.
Cardano base addresses combine two credentials: a payment credential and a stake credential. OWS derives payment and staking keys separately under CIP-1852, as documented in the Cardano integration pull request #244. Transactions are signed with the payment key, with a stake key signature added when required and available.
The integration was implemented by WingRiders in coordination with IOG and the Midnight Foundation, including technical review. It was merged into the OWS repository and included in version 1.4.3.
Source: OWS Cardano integration-Pull request #244.
This integration involves more than adding Cardano to a list of supported networks: OWS must account for Cardano’s key derivation, address structure, and transaction-signing requirements.
5.What Could OWS Mean for Cardano Developers and Users?
OWS offers developers a way to connect AI agents to blockchain wallets through a common interface and policy-based signing controls.
For Cardano developers, this creates opportunities to experiment with AI-powered dApps and automated blockchain services. Users could eventually benefit from applications that make certain blockchain interactions easier to automate while keeping permissions clearly defined.
The potential extends beyond Cardano, as developers across the wider blockchain ecosystem can explore similar use cases.
The next step is to test the integration and turn its potential into practical solutions for the community.
Looking Ahead
Cardano’s integration into the Open Wallet Standard brings AI and blockchain closer. Its real impact will depend on what developers build and how these solutions serve the ecosystem.
Perspectives and technical feedback are welcome to help deepen this discussion and strengthen our collective understanding of OWS.
Official resources
- IOG announcement: Open Wallet Standard adds Cardano support
- Open Wallet Standard —Official website · Source-code repository
- OWS — Supported Chains documentation
- OWS — Policy Engine documentation
- OWS Cardano integration — Pull request #244
- Cardano CIP-1852
- OWS v1.4.3 release notes
Building smarter. Securing better. Exploring what’s possible with Cardano.