Pimlico
- Name: Pimlico
- URL: https://www.pimlico.io/
- Category: Account-abstraction infrastructure / ERC-4337 bundler and paymaster platform
- Tags: ethereum-ecosystem
- Summary: Pimlico is ERC-4337 plumbing: bundlers, paymasters, sponsorship, and routing. That makes it useful, because a lot of
smart account UXrhetoric eventually cashes out as operator policy in exactly this layer. Strong infra vendor, not the account substrate. - What it does:
- Provides ERC-4337 infrastructure for smart accounts, including bundler and paymaster services
- Offers API endpoints and managed infra for relaying user operations and sponsoring gas fees
- Maintains open-source developer tooling including
permissionless.jsand theAltobundler - Supports developers building account-abstraction-enabled wallets, apps, and embedded onchain UX across Ethereum and EVM-compatible chains
- Positions itself as infrastructure for simplifying gas, nonce, and user-operation handling so product teams can focus on UX
- Key claims:
- Homepage describes Pimlico as “the world’s most trusted and advanced smart account infrastructure platform”
- Official docs describe it as “the world’s most advanced ERC-4337 account abstraction infrastructure platform”
- Docs say Pimlico provides tools and services to build, deploy, and manage smart accounts on Ethereum and other EVM-compatible chains
- Docs market paymasters that can sponsor gas fees on 100+ chains through a simple API endpoint
- Public GitHub repositories show both a high-level smart-account library (
permissionless.js) and an open-source ERC-4337 bundler (Alto)
- Whitepaper: No classic whitepaper or litepaper was found during this pass. Primary-source snapshots were saved in
../whitepapers/pimlico-primary-sources-2026-04-22.md. - Sources:
Internal linkages
Control surface
-
Pimlico is not the account substrate. It is the traffic layer around ERC-4337: bundlers, paymasters, sponsorship policy, retries, and routing.
-
That is why it matters. A lot of
wallet UX solvedtalk turns back into operator policy before a UserOperation ever lands onchain. -
The leverage is simple: what gets admitted, what gets sponsored, what degrades cleanly, and which chains or standards get first-class support.
-
Last reviewed: 2026-05-23 UTC