Having trouble finding the right infrastructure?

Request a free consultation

Having trouble finding the right infrastructure?

Request a free consultation

COMPANY detail

Open Wallet Standard
An open standard that unifies how agents interact with wallets

/

OPEN WALLET STANDARD
Company Overview.
Year Founded 2026
Status Open Source (MIT License)
Specialties Multi-Chain Wallet Infra
Maintained By MoonPay
Industry Developer Infrastructure
Location New York, USA
Description.

The Open Wallet Standard (OWS) is an open-source specification that gives AI agents and developer tools a secure, universal way to hold value, sign transactions, and pay for services across every major blockchain — without ever exposing a private key. For neobank builders deploying autonomous agents, OWS solves the foundational problem: there is no shared standard for how AI agents interact with wallets.

Every agent framework today rolls its own key management. Private keys end up in environment variables, plaintext config files, and proprietary formats. A wallet created for one agent cannot be used by another. OWS replaces this fragmentation with a single open standard: one encrypted vault on the user’s machine, one interface for every chain, and a security model where the private key is never exposed to the agent, the LLM, or any parent process.

OWS supports EVM (Ethereum, Base, Polygon, Arbitrum, Optimism), Solana, Bitcoin, Cosmos, Tron, TON, Sui, Filecoin, Spark, and XRP Ledger — all from a single seed. The standard ships with native SDK bindings for Node.js and Python, a CLI, and an MCP server interface.

The standard grew out of MoonPay’s own product development. MoonPay took the wallet infrastructure behind MoonPay Agents, generalised it across chains and runtimes, and released it under an MIT licence. Contributors include PayPal, OKX, Ripple, Circle, the Ethereum Foundation, Solana Foundation, Base, Polygon, Sui, TON Foundation, and Tron.

Trusted By PayPal · OKX · Ripple · Circle · Ethereum Foundation · Solana Foundation · Base · Polygon · Sui · TON Foundation · Tron

Key Infrastructure.
Multi-Chain from One Seed A single seed phrase derives accounts across EVM, Solana, Bitcoin, Cosmos, Tron, TON, Filecoin, Sui, Spark, and XRP Ledger. CAIP-2 and CAIP-10 addressing abstracts away chain-specific details.
Zero Key Exposure Keys are encrypted at rest using AES-256-GCM, decrypted only to produce a signature, held in protected memory that cannot be swapped to disk, and wiped immediately after. Private keys never pass through the LLM context.
Policy Engine A pre-signing policy engine gates agent operations before any key material is touched. Supports chain allowlists, expiry, spending limits, and optional custom executables.
Local-First Architecture The wallet vault lives at ~/.ows/ on the user’s machine. No cloud accounts, no remote key management, no network dependency for signing.
Native SDKs Fully self-contained language bindings for Node.js and Python that embed the Rust core via native FFI. Install via npm, PyPI, or build from source.
MCP Server Interface Works with any tool that speaks JSON — CLI, MCP, SDK, REST. Agents built on any MCP-compatible framework access wallets through their native tool system.
Additional Features.
MIT Licensed
Fully open source. Anyone can use, modify, and distribute freely.
10+ Chain Families
EVM, Solana, Bitcoin, Cosmos, Tron, TON, Filecoin, Sui, Spark, and XRP Ledger from a single wallet.
15+ Contributing Organisations
PayPal, Circle, OKX, Ripple, Ethereum Foundation, Solana Foundation, and more.
No Vendor Lock-In
No HTTP. No authentication flows. No rate limits. No subscription. Runs entirely on your machine.
Portable Wallets
A wallet created by one tool works in every other. No more scattered balances across agent-specific keystores.
Hackathon Active
OWS hackathon running at hackathon.openwallet.sh with multiple build rounds.

Seamlessly Works With.

GENERAL Questions.

What problem does OWS solve for neobank builders?
If you are deploying AI agents that need to move value — trading agents, treasury agents, payment agents — each one currently needs its own wallet integration. OWS gives every agent a single, shared wallet layer. One vault, one interface, portable across tools and chains.
How is OWS different from existing wallet SDKs?
Existing wallet SDKs are either chain-specific, cloud-dependent, or designed for browser extensions. OWS is local-first, multi-chain from one seed, and designed specifically for programmatic agent access with a pre-signing policy engine.
Is OWS a MoonPay product?
OWS originated from MoonPay’s internal infrastructure for MoonPay Agents, but it is released under an MIT licence and maintained as an open standard with contributions from 15+ organisations.
How does OWS relate to payment protocols like x402 or MPP?
Protocols like Coinbase’s x402 and Stripe’s Machine Payments Protocol define how agents pay for things. OWS defines where the wallet lives and how agents sign transactions. Any protocol that requires a signed transaction now has a common wallet to call.

Verified Team

This company has been verified by TODEY team. They have direct access to its data and actively monitor it to keep information accurate and up to date.

Learn More