Alto

• Name: Alto
• URL: https://docs.pimlico.io/references/bundler
• Category: ERC-4337 bundler implementation / self-hostable user-operation admission and submission layer
• Tags: ethereum-ecosystem
• Summary: Alto is Pimlico’s open-source ERC-4337 bundler. Small but useful. The value is that it exposes simulation, admission, executor funding, retries, and chain-specific handling directly instead of burying them inside smart-account marketing.
• What it does:
  • Implements the ERC-4337 bundler role for supported EVM chains in TypeScript
  • Receives, simulates, validates, and submits UserOperations instead of acting as the smart-account layer itself
  • Supports self-hosting with executor wallets and a utility wallet that can refill executors below configured thresholds
  • Offers a safe mode tied to ERC-7562-style validation and RPC support such as debug_traceCall
  • Exposes chain-specific configuration for environments including legacy-transaction networks, OP Stack chains, and Arbitrum chains
• Key claims:
  • Pimlico presents Alto as its bundler implementation, with speed and inclusion reliability as the commercial pitch
  • The self-host guide makes clear that executor-wallet management and refill policy are part of the real control surface
  • Validation strictness depends partly on RPC capabilities, so some of the trust and failure model is inherited from the operator’s infra choices
  • Chain-specific flags make the practical point: bundler behavior is not truly chain-neutral
  • Alto ships as a visible standalone service and repo instead of disappearing behind generic smart account product language
• Whitepaper: No standalone Alto whitepaper or litepaper surfaced in this pass. The clearest current sources were Pimlico’s bundler docs, self-host guide, and the public Alto repository/README; see ../whitepapers/alto-primary-sources-2026-05-10.md.
• Sources:
  • https://docs.pimlico.io/references/bundler
  • https://docs.pimlico.io/references/bundler/self-host
  • https://github.com/pimlicolabs/alto
  • https://raw.githubusercontent.com/pimlicolabs/alto/main/README.md
  • https://github.com/pimlicolabs

Internal linkages

• Best anchors: pimlico, erc-4337, and erc-7562.

Protocol / company boundary

• Keep this note on the self-hostable bundler implementation: simulation, admission, executor-wallet funding, refill policy, retries, and chain-specific handling.
• Use pimlico when the sharper question is who issues API keys, runs the hosted bundler and paymaster endpoints, fronts gas, and wraps Alto inside a dashboard, billing, and support shell.
• That split matters because Alto is the specific open-source implementation, while Pimlico is the named operator boundary many teams inherit first.

Control surface

• Alto is the ERC-4337 admission-and-submission layer. The leverage sits in simulation rules, local policy, executor capital, retry behavior, and chain-specific flags.

• That is the point of the note. A lot of smart account UX still depends on a bundler deciding what gets admitted, retried, or dropped.

• Treat Alto as self-hostable bundler plumbing under the broader Pimlico umbrella, not as a peer to larger wallet-control platforms.

• Last reviewed: 2026-06-06 UTC