Open Wallet

OWS is a unified local storage format to create, sign, and manage wallets securely across every tool and chain. Start: openwallet.sh Docs: docs.openwallet.sh Github: github.com/open-wallet-st…

x402 = how agents pay OWS = how they sign Both needed. Now the stack actually composes.

OWS is a unified local storage format to create, sign, and manage wallets securely across every tool and chain. Start: openwallet.sh Docs: docs.openwallet.sh Github: github.com/open-wallet-st…

x402 + OWS = Agentic Payments

@hitdex 🫡🫡🫡

Don't tempt me with a good time!

MoonPay just open-sourced OWS - a local-first protocol that gives AI agents and developer tools a single way to: - Store keys. - Manage wallets. - Sign transactions across any chain. Right now, every AI agent that wants to do anything onchain has to reinvent the wallet layer from scratch - different key storage, different signing logic, different chain support. There's no shared foundation. OWS wants to fix that. Here's what it does: - Stores private keys locally (you keep custody) - Gives agents a unified way to sign transactions across any chain - Works across 170 chains and 700+ assets (inc. $USDT, $WBTC, and $PYUSD) via LayerZero PayPal, Solana, and Ripple are all behind it. When payment rails and major L1s align on a single wallet standard, it means they want AI agents moving real money on their chains/platforms. Kinda like what HTTP did for the web. Before HTTP, the internet ran on a range of protocols with information locked in silos. After HTTP, everything connected through a universal standard. OWS is trying to be the HTTP for AI wallets. Whether that happens depends on developer adoption. Standards live and die on distribution.

JUST IN: SUI BACKS NEW WALLET STANDARD TO FIX MULTI-CHAIN FRAGMENTATION 🤯🤯🤯 OWS enables multi-chain wallet control with a single seed phrase, tackling fragmentation and key management risks

Agent payment stack is coming together faster than expected. MoonPay just open-sourced @OpenWallet, a local-first protocol for how agents hold keys and sign transactions. And this isn’t happening in isolation. Over the past few weeks, x402 added ERC-20 token support and SIWX authentication, MPP introduced payment-method-agnostic flows with streamed payments, and now OWS fills in the wallet layer underneath both of them. Each piece solves a different part of the puzzle. x402 and MPP handle how agents pay. OWS handles how keys are stored and used for signing. Keys get decrypted in an isolated process, held in mlocked memory, and wiped right after signing. The agent itself never has direct access to key material. The design choice that stands out is local-first. No cloud KMS, no custodial APIs. The vault lives on the machine and signing happens instantly without a network round-trip. As more agents move toward self-hosted setups, this direction makes a lot of sense. The coalition behind it is worth noting too. PayPal, OKX, Ripple, Ethereum Foundation, Solana Foundation, Circle, Polygon, Base, LayerZero, TON Foundation. 21 organizations at launch. Three open standards, each covering a different layer, all emerging within weeks of each other. The stack is taking shape.

Read more here:

@SwiftBovine @maxwallenberg @Maurathat yes, imminent

@maxwallenberg @Maurathat @OpenWallet Any plans for XRPL support?

Today we are launching OWS @OpenWallet - an open standard that unifies how agents interact with wallets. OWS is built open-source with support from: PayPal, OKX, Ripple, Tron, TON, Solana, Ethereum, Base, Polygon, SUI, Filecoin, LayerZero, DFlow, Circle, Uniblock, Virtuals, Arbitrum, Dynamic, Allium, and Simmer Markets Start: openwallet.sh Docs: docs.openwallet.sh Github: github.com/open-wallet-st…

“because the number of agents that need wallets is growing faster than the number of wallet standards.”

tl;dr on the Open Wallet Standard (OWS): ◻️ open-source protocol for how AI agent wallets store keys, sign transactions, and work across chains ◻️ one vault, one interface, every chain (EVM, Solana, Bitcoin, TON, Cosmos) ◻️ local-first: keys live on your machine, never leave it, never touch the cloud ◻️ sits underneath x402, MPP, AP2, and every other payment protocol ◻️ 21 founding orgs including MoonPay, PayPal, Ripple, Circle, Solana Foundation, Ethereum Foundation, Base ◻️ standardizes a layer where every agent framework was rolling its own implementation with keys scattered across env files in incompatible formats ◻️ live today, three lines of code to create a wallet the stack is filling in fast. wallets, payments, identity, checkout, authorization. the piece that still needs building is the controls layer that defines what an agent is allowed to do with that wallet once it has one.

Just install and test a @OpenWallet by @moonpay on my agent looks cool 🤍

The world is changing rapidly and agents need to be able to operate seamlessly on any chain. With 300+ Blockchains, 55+ Data Partners, and 3000+ APIs, Uniblock has every blockchain API in one interface. Uniblock is proud to be among the first 15+ founding contributors to OWS alongside @moonpay

@circle @solana @moonpay @PayPal 🤝

@solana @moonpay @PayPal 🤝

.@MoonPay just open-sourced a wallet standard for AI agents, backed by 15+ contributors including @Solana, @PayPal and @Circle One seed phrase gives you wallets on EVM, Solana, Bitcoin, XRP, and more

Reminder that @moonpay agents uses @openwallet One command to try it out: npm I-g @moonpay/cli

Pleased to be part of this standard and launch with Sui support! OWS is a great way to have your chain agnostic coding agent experiment with Sui and Walrus differentiators to see if they’re a good fit for what you’re building. Eg, try asking your agent to benchmark a payment in all supported chains and see who wins in latency/cost!

npm install -g @open-wallet-standard/core

@OrinBase @maxwallenberg yes

@maxwallenberg @OpenWallet okay this is bigger than it looks