For Wallets
The infrastructure behind the biggest wallets onchain
MetaMask, Safe, and Trust Wallet run smart account transactions on Pimlico. Whatever signer architecture you choose, the execution layer is already built.
Why wallets choose Pimlico
Ship wallet UX users expect from web2
Your installed base
Your existing users go gasless. No migration.
A wallet's hardest constraint is its installed base: millions of existing users on plain EOAs who cannot be asked to move funds or change addresses. Pimlico sponsors batched, gasless transactions straight from those existing accounts, so smart account features ship to the users you already have, not just new signups.
Powered by EIP-7702 and ERC-5792, live today.
EOA signs an authorization
An ordinary wallet account, with no smart contract deployed and no assets moved.
Pimlico sponsors and bundles
The paymaster verifies your policy and pays the gas, same as any smart account.
Transaction confirmed
The account is unchanged: the user kept their address and their keys.
Works with your stack
Every signer. Every smart account.
Pimlico sits below your key management layer, so whichever architecture you pick, it already works.
Smart accounts
Social login
Passkeys
Key management
No lock-in
If it can sign, it works
The catalog above is the documented fast path, not a whitelist. Any viem-compatible signer (a LocalAccount, an EIP-1193 provider, or a WalletClient) plugs in as the smart account owner.
So choose key management for product reasons: if you re-platform signers later, the switch never touches your transaction infrastructure.
// Any viem-compatible signer works as an owner:
// a LocalAccount, an EIP-1193 provider, or a WalletClient.
const owner = privateKeyToAccount("0x...") // local key
// const owner = await providerToSmartAccountSigner(eip1193Provider)
const account = await toSafeSmartAccount({
client: publicClient,
owners: [owner], // Privy, Turnkey, passkeys: if it can sign, it works
version: "1.4.1",
})Every network your users expect, one integration
Wallet scale
Infrastructure that holds when your wallet spikes
Serving millions of users means traffic bursts, re-orgs, and support tickets. Everything between “user tapped” and “confirmed on-chain” is the engine's job, not yours.
In production
What the biggest wallets run on Pimlico
Proven at scale
Infrastructure your wallet can stake its name on
Frequently asked questions
Which smart accounts and signers work out of the box?
Every major smart account works out of the box, including Safe, Kernel, MetaMask Smart Accounts, and Coinbase Wallet, and any viem-compatible signer can be the owner: social login, passkeys, or institutional custody. If you are starting fresh, permissionless.js creates accounts in a few lines.
Can our existing EOA users go gasless without migrating?
Yes. With EIP-7702, Pimlico sponsors batched, gasless transactions straight from existing EOAs. Your users keep their address and their keys, and nothing about their account changes.
Can we run the bundler ourselves?
Alto, the bundler behind Pimlico’s infrastructure, is open source and you are free to run it. Wallet teams use the hosted platform for the multi-chain coverage, monitoring, SLAs, and the sponsorship engine on top.
Which chains can our wallet support?
All 100+ chains Pimlico runs on, including Ethereum, Base, Arbitrum, Optimism, Polygon, and Gnosis, through one integration. If your users need a chain we have not launched yet, talk to us. We partner with new chains continuously.