Open Wallet Standard (OWS)
Open, local-first standard + CLI/SDK for agent wallets: encrypted keystore, policy checks before signing, scoped tokens instead of keys.
- Sato Score72
- ChainsBitcoin, Ethereum +4
Open Wallet Standard (OWS) is an open-source wallet infrastructure on Bitcoin, Ethereum, Solana and other chains, with last code activity on 2026-11-06 (Active). Latest release on 2026-09-29. Sato Score 72/100 (how open, active and verifiable it is, not a safety grade), as of 2026-11-07. How the score works →
Check what an install would ask of your keys, before you run it →Last commit Nov 6, 2026 · Last release Sep 29, 2026 (v1.4.3) · ★ 377
Listed from openwallet.sh on 2026-09-23. Install: not attempted — no install path on record. Evidence →
Next step
Watch Open Wallet Standard (OWS)
One email if what we observe changes — its repo goes quiet or disappears, or the listing is retired. Nothing else.
Check it from your agent
Add Sato Hub’s MCP server (no key), then ask:
https://satohub.ai/api/mcpRun Sato Hub Preflight on open-wallet-standard/core before I use it.Your project?
Prove you control the domain and correct this page — description, links, tags, chains. A claim proves control, not verification: it never changes the Sato Score.
Claim this listing →Overview
MoonPay open-sourced OWS in March 2026 (PR Newswire). openwallet.sh describes it as a local-first standard: keys are encrypted with AES-256-GCM under ~/.ows, policy checks run before any key is used, and agents authenticate with scoped API tokens rather than seeing plaintext keys. It ships as @open-wallet-standard/core on npm, with PyPI and crates.io packages, and has MCP, SDK, CLI and REST interfaces. The GitHub repo is MIT, has 370 stars and was last released as v1.4.2 on 2026-06-19.
Sato Score
72/100· HighHow open, active & verifiable — not a safety or returns grade.
- Maintenance & liveness
- 35/35
- Code transparency
- 19/20
- Interface verifiability
- 0/10
- Docs & demo
- 6/10
- Listing transparency & provenance
- 9/15
- Independent verification
- 3/10
Evidence — listed vs checked · what the words mean
Listed from openwallet.sh on 2026-09-23. Install: not attempted — no install path on record.
| Claim | Value | Evidence | Source | Checked |
|---|---|---|---|---|
| Chains supported | Bitcoin, Ethereum, Solana, Cosmos, Tron, TON | self-reported | docs.openwallet.sh | as of 2026-11-07 |
| Verification status | Self-Reported — not independently reviewed | self-reported | openwallet.sh | as of 2026-11-07 |
| Recent activity | last release 2026-09-29 · last commit 2026-11-06 | observed | github.com/open-wallet-standard/core | 2026-11-07 |
| Website answers | answered (HTTP 200) | observed | openwallet.sh | 2026-11-07 |
| Daily check record | 45 of 45 daily checks since 2026-09-23 succeededa success rate of our checks, not uptime; the source is this listing's own history | observed | — | 2026-11-06 |
| Deploys as | CLI, SDK, MCP, REST API, Local/self-hostedconfidence 0.85 | self-reported | openwallet.sh | as of 2026-09-26 |
| Tags | key-management, policy-engine, open-standard, self-custody, mcp, multi-chain, c…confidence 0.80 | self-reported | openwallet.sh | as of 2026-09-26 |
| Sato Score | 72/100 (High)how open, active and verifiable — not a safety or quality grade | computed | satohub.ai | 2026-11-07 |
Self-reported rows are the project’s own words, dated when we recorded them — not a check. Only reproduced and reviewed rows carry a mark. None of these rows is a safety or quality rating.
Observed record — 46 daily checks since 2026-09-23
- Succeeded
- 46
- Failed
- 0
- Their error
- 0
- Unattributed
- 0
This is the share of our daily checks that succeeded — not an availability guarantee. A check can fail because the host was down, because our runner timed out, or because the network in between dropped it, and only the first of those is a fact about this project. Failures are split by what we can attribute; anything we cannot attribute is counted, not hidden.
Last 30 days — to 2026-11-07, one point per UTC day
A gap is a day we have no attributable observation — never a zero. Thirty points is the whole shape the free layer carries; the daily rows behind it stay in the snapshot series.
Details
- Chains
- Bitcoin, Ethereum, Solana, Cosmos, Tron, TON
- Agent types
- Standard, Agent Wallet
- Open source
- Yes
- Deploys as
- CLI, SDK, MCP, REST API, Local/self-hosted
- Last checked
- 2026-11-07
Marketplace Signals
No marketplace signals recorded for this resource yet.
Verification status reflects evidence reviewed by Sato Hub. Self-reported claims are never presented as verified.
Where Open Wallet Standard (OWS) fits
Related concepts: How Agents Use Wallets, What Are Onchain Agents?
Recent Activity
All news →Releases and posts from Open Wallet Standard (OWS), pulled from its GitHub and X.
Listing History
Recorded changes to Open Wallet Standard (OWS)'s listing — status, verification, Sato Score, and recent releases. Full history is kept in the listing record.
- Sep 29, 2026New release published
- Sep 26, 2026Auto-enriched: tags, deployment options
- Sep 23, 2026Listed on Sato Hub
- Sep 23, 2026Sato Hub began tracking this listing
Compared with
Appears in
Related Resources
Coinbase AgentKit
ActiveCoinbase's toolkit for giving AI agents wallets and the ability to take onchain actions.
Hyperliquid
ActiveOnchain perpetual futures and spot DEX running on its own L1 with an HyperEVM smart-contract layer.
Model Context Protocol (MCP)
ActiveAnthropic's open standard for connecting AI systems to external tools and data sources.
Reference
QuestionsWhat people ask about this pageShowHide
Questions people ask about Open Wallet Standard (OWS)
- Is Open Wallet Standard (OWS) open source?
- Yes. Open Wallet Standard (OWS) is open source; the repository is https://github.com/open-wallet-standard/core. Checked as of 2026-11-07.
- Which chains does Open Wallet Standard (OWS) support?
- Open Wallet Standard (OWS) lists support for Bitcoin, Ethereum, Solana, Cosmos, Tron, TON as of 2026-11-07.
- Is Open Wallet Standard (OWS) still maintained?
- The most recent code activity Sato Hub observed was on 2026-11-06 (last commit 2026-11-06, last release 2026-09-29), which Sato Hub labels "Active". Posts on X are not counted as maintenance. Activity is a recency signal, not a quality judgment.
- How do I install or run Open Wallet Standard (OWS)?
- Sato Hub has no deploy spec for Open Wallet Standard (OWS); follow the project's own documentation at https://docs.openwallet.sh/.
- Is Open Wallet Standard (OWS) verified on Sato Hub?
- No independent verification is on record for Open Wallet Standard (OWS); its verification status is "Self-Reported" and its Sato Score is 72 of 100. Self-reported is not verified, and the score is not a safety, quality or returns grade.
Cite this pagePlain text, APA or BibTeXShowHide
Cite this page
Sato Hub. "Open Wallet Standard (OWS) — Sato Hub." Sato Hub, updated 2026-11-07, accessed 2026-11-07. https://satohub.ai/resources/open-wallet-standardData last refreshed 2026-11-07; this page is rebuilt daily. Citations carry the date so a reader can tell which snapshot a claim came from. Catalog data is licensed CC-BY-4.0.
Join the Sato Hub Briefing
Sign up for the Briefing: the agents, tools, and infrastructure that actually shipped, and why they matter.