ZeroDev
ERC-4337 smart-account SDK (Kernel) with session keys, gas sponsorship, and batched transactions for agent wallets.
- Sato Score48
- ChainsMultichain
ZeroDev is a partly open-source wallet infrastructure, with no code activity tracked. Sato Score 48/100 (how open, active and verifiable it is, not a safety grade), as of 2026-10-21. How the score works →
See how to install ZeroDev →No code activity tracked
Listed from zerodev.app on 2026-07-19. Install: not attempted. Evidence →
Next step
Check it from your agent
Add Sato Hub’s MCP server (no key), then ask:
https://satohub.ai/api/mcpAsk Sato Hub what is on record about ZeroDev 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
ZeroDev provides smart-account infrastructure built on ERC-4337 (its Kernel implementation co-authors ERC-7579), offering session keys, gas abstraction, transaction batching, and cross-chain funding routing behind a single API. It reports 10M+ smart accounts deployed and $2B+ in monthly transaction volume across 130+ networks, and is positioned for agent frameworks that need programmable, non-custodial wallet control rather than raw EOA key management.
Sato Score
48/100· MediumHow open, active & verifiable — not a safety or returns grade.
- Maintenance & liveness
- 20/35
- Code transparency
- 12/20
- Interface verifiability
- 0/10
- Docs & demo
- 6/10
- Listing transparency & provenance
- 7/15
- Independent verification
- 3/10
Sato Check
v5.5.11 · as of 2026-10-17- Does it take your key?
- Asks for a key
- Does your key leave?
- Not yet run
- Can it move funds on its own?
- Unknown
A profile describes what we read and ran, with dates. It is not a safety rating, an audit or an endorsement, and "not found" is not "not there".
Evidence — listed vs checked · what the words mean
Listed from zerodev.app on 2026-07-19. Install: not attempted.
| Claim | Value | Evidence | Source | Checked |
|---|---|---|---|---|
| Chains supported | Multichain | self-reported | docs.zerodev.app | as of 2026-10-21 |
| Verification status | Unverified — not independently reviewed | self-reported | zerodev.app | as of 2026-10-21 |
| Install works | documented by the project, not run by Sato Hubnot attempted: no falsifiable install+entry probe from deploy_spec | self-reported | docs.zerodev.app | as of 2026-09-14 |
| Website answers | answered (HTTP 308) | observed | zerodev.app | 2026-10-21 |
| Daily check record | 90 of 90 daily checks since 2026-07-23 succeededa success rate of our checks, not uptime; the source is this listing's own history | observed | — | 2026-10-20 |
| Takes your key | asks for a private key or seed phrase | declared | satohub.ai | as of 2026-10-17 |
| Key leaves the machine | not yet run with planted test keysthe sandbox lane has not run on this version | observed | satohub.ai | not dated |
| Moves funds on its own | unknown — could not read what it exposes | traced | satohub.ai | 2026-10-17 |
| Sato Score | 48/100 (Medium)how open, active and verifiable — not a safety or quality grade | computed | satohub.ai | 2026-10-21 |
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.
Install — not run by us — no falsifiable install+entry probe from deploy_spec
Runtime: Node.js (npm packages @zerodev/sdk + @zerodev/ecdsa-validator)
npm i @zerodev/sdk @zerodev/ecdsa-validator
npm i --save-dev @types/node tslib
import { createKernelAccount, createKernelAccountClient, createZeroDevPaymasterClient } from "@zerodev/sdk"; import { signerToEcdsaValidator } from "@zerodev/ecdsa-validator"You supply: ZeroDev RPC URL (project-scoped endpoint from the ZeroDev dashboard), A signer private key — the quickstart generates one locally via viem generatePrivateKey(); RISK: a production deployment supplies its own signing key
Read from the project’s own docs as of 2026-09-14. What a deploy spec is →
Observed record — 91 daily checks since 2026-07-23
- Succeeded
- 91
- 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. 40 of these checks predate 2026-09-01, when the probe counted a bot-block (HTTP 403) as a failure and recorded no reason for any failure. Every one of them passed, so the rate covers them too.
Last 30 days — to 2026-10-21, 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.
Measured on-chain — week 2026-W43
What we can observe about this project on-chain, from public reads, with the method and sample size attached to every figure. A raw deployment count is not an adoption figure and is shown separately below.
Context only — total deployments including humans
Coinbase Smart Wallet is the same contract behind consumer Coinbase Wallet; every factory here serves ordinary humans. These numbers describe a market, not agents.
Rates on fewer than 20 observations are shown but not quotable. Full venue detail: ERC-4337 smart accounts · The onchain agent economy.
Where this listing appears in the agent economy — week 2026-W43, 4 measured cells
- ERC-4337 smart accountsArbitrumDeployed
- ERC-4337 smart accountsEthereumDeployed
- ERC-4337 smart accountsOptimismDeployed
- ERC-4337 smart accountsPolygonDeployed
Each cell is one venue × chain × stage in the weekly series, attributed to this listing as a producing platform or seller. Figures, evidence tier and sample size are in the panel above; the cells are never summed. Whole series →
Details
- Chains
- Multichain
- Agent types
- Smart-account SDK
- Open source
- Partial
- Last checked
- 2026-10-21
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.
Listing History
Recorded changes to ZeroDev's listing — status, verification, Sato Score, and recent releases. Full history is kept in the listing record.
- Jul 24, 2026Sato Hub began tracking this listing
- Jul 20, 2026Edited: deploy spec
- Jul 19, 2026Listed on Sato Hub
Compared with
Appears in
Related Resources
Bankr
ActiveCrypto execution layer and cross-chain wallet that lets agents and users trade, bridge, and manage assets via natural language, plus a skills marketplace and an x402 cloud for spinning up pay-per-call agent endpoints.
Privy
ActiveEmbedded and server wallet infrastructure used to give agents secure key management.
Trust Wallet Agent Kit (TWAK)
ActiveNon-custodial toolkit from Trust Wallet (MCP server, CLI, and SDK) that lets AI agents read and transact across 25+ chains within user-defined rules.
Reference
QuestionsWhat people ask about this pageShowHide
Questions people ask about ZeroDev
- Is ZeroDev open source?
- Partly. Some of ZeroDev is published as source (https://github.com/zerodevapp) and some is not. Checked as of 2026-10-21.
- Which chains does ZeroDev support?
- ZeroDev lists support for Multichain as of 2026-10-21.
- Is ZeroDev still maintained?
- Sato Hub tracks no commit or release for ZeroDev; it cannot say whether it is maintained.
- How do I install or run ZeroDev?
- Node.js (npm packages @zerodev/sdk + @zerodev/ecdsa-validator). Install: npm i @zerodev/sdk @zerodev/ecdsa-validator && npm i --save-dev @types/node tslib. Entry: import { createKernelAccount, createKernelAccountClient, createZeroDevPaymasterClient } from "@zerodev/sdk"; import { signerToEcdsaValidator } from "@zerodev/ecdsa-validator". This is taken from the project's own documentation and has not been reproduced by Sato Hub.
- Is ZeroDev verified on Sato Hub?
- No independent verification is on record for ZeroDev; its verification status is "Unverified" and its Sato Score is 48 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. "ZeroDev — Sato Hub." Sato Hub, updated 2026-10-21, accessed 2026-10-21. https://satohub.ai/resources/zerodevData last refreshed 2026-10-21; 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.