Candide

• Name: Candide
• URL: https://www.candide.dev/
• Category: Safe-based smart-wallet infrastructure / hosted account-abstraction operations
• Tags: ethereum-ecosystem
• Summary: Candide is Safe-based account-abstraction tooling for teams that want managed bundler and paymaster plumbing. The Safe base is the real anchor. The rest is hosted execution middleware around it.
• What it does:
  • Provides a developer platform for building Ethereum smart wallets with passkeys, batch transactions, gas sponsorship, ERC-20 gas payments, multisig, and recovery flows on top of Safe contracts
  • Ships AbstractionKit, a TypeScript SDK for building and sending ERC-4337 UserOperations across Safe accounts, Calibur accounts, and simple EIP-7702 accounts
  • Operates bundler, paymaster, dashboard-managed gas sponsorship policy, and recovery tooling for production use
  • Markets the stack into payment, treasury, stablecoin-wallet, and agent-wallet use cases where teams want managed wallet operations rather than raw protocol components
  • Maintains public repos for SDKs, examples, contracts, audits, and the Voltaire ERC-4337 bundler
• Key claims:
  • Candide describes itself as smart-account infrastructure for payments, wallets, and neobanks and stresses open-source / no-lock-in positioning across EVM chains
  • Candide says the accounts remain self-custodial because they live onchain as Safe smart accounts and can use Candide passkeys or external signers without key shards
  • The developer docs frame the product around UX and ops improvements: gasless or ERC-20 gas payments, passkey onboarding, spending controls, batching, multisig, and recovery
  • AbstractionKit claims vendor-agnostic support across Ethereum interface libraries, bundlers, and paymasters while still giving first-class treatment to Safe and EIP-7702 paths
  • The paymaster docs make the operational point clearly: Candide exposes live JSON-RPC sponsorship infrastructure, not just an SDK wrapper
• Whitepaper: No whitepaper or litepaper was found during this pass. The strongest primary materials were the official site, developer docs, AbstractionKit introduction, Paymaster API reference, and GitHub organization; see ../whitepapers/candide-primary-sources-2026-04-25.md.
• Sources:
  • https://www.candide.dev/
  • https://docs.candide.dev/
  • https://docs.candide.dev/wallet/atelier-intro/
  • https://docs.candide.dev/wallet/abstractionkit/introduction/
  • https://docs.candide.dev/wallet/paymaster/rpc-methods/
  • https://github.com/candidelabs

Internal linkages

• Best anchors: safe, pimlico, and biconomy.

Governance / control risk

• The Safe base is the part worth reading.

• The leverage sits in the managed layer around it: bundler admission, paymaster policy, sponsorship rules, recovery defaults, SDK behavior, and routing.

• Treat Candide as hosted AA operations wrapped around Safe, not as some new account primitive.

• Last reviewed: 2026-05-27 UTC