# ZeroDev

> Smart account infrastructure for ERC-4337 and EIP-7702 apps, including Kernel accounts, bundlers, paymasters, session keys, gas sponsorship, and chain abstraction.

- Readiness score: **100/100** (score.v2)
- Integration difficulty: medium
- Chains: ethereum, arbitrum-one, base, optimism, polygon, bsc, avalanche, base-sepolia
- Categories: accounts, paymasters, gasless, wallets, automation, chain-abstraction
- Last verified: 2026-06-10 by composewith.eth research (ZeroDev docs, website, SDK, examples, Kernel repo, gas sponsorship, permissions, and chain abstraction docs live-verified via WebFetch 2026-06-10) (confidence: high)

## Resources

- docs: https://docs.zerodev.app/
- sdk: https://github.com/zerodevapp/sdk
- template: https://github.com/zerodevapp/zerodev-examples
- support: https://discord.gg/KS9MRaTSjx

## Good for

- smart accounts
- gasless onboarding
- session keys and permissions
- EIP-7702 experiments
- chain-abstracted balances and cross-chain UX
- apps pairing embedded wallets with account abstraction

## Avoid for

- teams that need fully self-hosted bundler and paymaster infrastructure from day one
- apps that cannot depend on provider-managed gas policies, RPCs, relays, or plan limits

## Capabilities

### Kernel smart accounts (production-ready)
Best for: ERC-4337 smart account apps, EIP-7702-compatible account abstraction flows, modular account plugins
- Kernel version, EntryPoint version, validator choice, and chain support must be chosen deliberately before production.

### Gas sponsorship and paymaster flows (production-ready)
Best for: gasless onboarding, sponsored UserOps, ERC20 gas payment flows
- Gas policies must be configured before sponsorship works; reaching policy or account-level limits can make UserOps fail unless fallback middleware is implemented.

### Permissions and session keys (production-ready)
Best for: AI agent transaction constraints, temporary delegated keys, policy-bounded automation
- Permissions require explicit signer, policy, and action design; weak policies can over-delegate account authority.

### Chain abstraction (beta)
Best for: spending balances across chains without manual bridging, USDC, USDT, WETH, and ETH cross-chain flows, apps willing to manage plan limits and solver-dependent execution
- Production chain abstraction requires Scale or Enterprise plan access; network and token coverage are narrower than generic EVM chain support.

### Embedded smart wallet (beta)
Best for: standalone embedded smart account UX, apps replacing seed-phrase wallet flows, teams tracking ZeroDev's July production-readiness milestone
- Treat the embedded smart wallet surface as beta until ZeroDev marks it production-ready; verify docs and support commitments before production launch.

## Composes with

- **privy** (wallet_and_identity; supports) — Privy or Dynamic-style WaaS products can handle user auth and embedded wallet onboarding while ZeroDev provides the smart account, paymaster, bundler, and permission layer.
- **biconomy** (transactions_and_paymasters; alternative) — Biconomy is a separate account-abstraction provider for gasless onboarding and sponsored transactions; choose between providers based on chain support, pricing, SDK fit, and operational requirements.
- **safe** (operational_controls; supports) — Safe can manage team treasury and admin operations around a ZeroDev-powered consumer app or marketplace.
- **erc-8004** (agent_identity_and_trust; supports) — ZeroDev session keys and permissions can constrain agent actions while ERC-8004-style registries provide agent identity, discovery, reputation, and validation signals.

## Known issues

- **Gas sponsorship needs policy and fallback design** (medium, confirmed) — workaround: Configure gas policies before launch, monitor usage limits, and implement paymaster fallback middleware for actions that should proceed without sponsorship.
  - source: https://docs.zerodev.app/smart-accounts/sponsor-gas/evm (retrieved 2026-06-10, high)
  - source: https://docs.zerodev.app/smart-accounts/sponsor-gas/evm (retrieved 2026-06-10, high)
- **Chain abstraction has token, network, and pricing limits** (medium, confirmed) — workaround: Before production, verify the exact input/output chains, supported tokens, gas-token mode, and plan tier for each user flow.
  - source: https://docs.zerodev.app/cross-chain/chain-abstraction/overview (retrieved 2026-06-10, high)
  - source: https://docs.zerodev.app/cross-chain/chain-abstraction/overview (retrieved 2026-06-10, high)

---
Canonical: https://composewith.eth/protocols/zerodev · JSON: https://composewith.eth/protocols/zerodev.json