For Chains & Ecosystems
Bring the gas sponsorship engine to your chain
One enterprise deal puts Pimlico's complete suite live on your chain: gas sponsorship, ERC-20 gas payments, policy controls, transaction infrastructure, and dashboards. Every builder in your ecosystem ships better user experience from day one.
The full suite
Everything Pimlico runs, running on your chain
A deployment is not a single service. It is the whole platform your builders would otherwise have to wait for, live on your chain at once.
Dashboards & analytics
Per-app spend, transactions, and active users. Your foundation sees exactly what the suite is doing for the ecosystem.
How it works
From first call to live ecosystem
We are live on 100+ chains and onboard new ones continuously, so a deployment is routine for us, not a project. If you are launching an L2, an L3, or an appchain, the suite can be running before your mainnet is.
Every deal is bespoke: deployment, support, and an optional gas program shaped around your launch. The first step is a conversation.
Intro call
We scope your chain, your stack, and your launch timeline.
Testnet deployment
Bundlers and paymasters go live on your testnet, so builders integrate before mainnet exists.
Mainnet launch
The full suite and dashboards are live the day your chain is.
Ecosystem gas program
The optional growth layer: fund sponsored gas for the teams building on you.
What your foundation sees
Every transaction on your chain, accounted for
Every operation on your chain is traceable in the dashboard from received to included on-chain, with millisecond timestamps and transaction hashes at each step. Spend is itemized per app, per policy, and over time.
Custom alerts fire before a program budget is hit, not after sponsorship stops — so when your foundation asks what the suite is doing for the ecosystem, the answer takes seconds, not a meeting.
Track user operation
Received
2026-06-11 20:01:13.054
Added to Mempool
2026-06-11 20:01:13.054 (+0ms)
Submitted
2026-06-11 20:01:13.341 (+287ms)
Tx Hash: 0x223b701f...Included Onchain
2026-06-11 20:01:13.590 (+249ms)
Tx Hash: 0x223b701f...Why ecosystems do it
Builder experience is chain growth
One deal covers every builder
No per-team infrastructure negotiations. Every app on your chain gets the same production suite from day one.
Day-one parity with the biggest L2s
Builders compare your chain's UX to Base and Arbitrum. Launch with the same gasless stack that already serves them.
The smart account developer base arrives with you
permissionless.js developers, the largest smart account community, can deploy to your chain with a one-line config change.
Day-one parity
The code your builders already wrote
This is the exact snippet the largest smart account SDK ships with — permissionless.js, at 100k+ weekly downloads. Pointing it at your network means changing the chain in the URL and the chain line. Nothing else.
Every team already running this code on Base or Arbitrum is one config change away from running it on you.
import { createSmartAccountClient } from "permissionless"
import { toSafeSmartAccount } from "permissionless/accounts"
import { createPimlicoClient } from "permissionless/clients/pimlico"
import { http, parseEther } from "viem"
import { base } from "viem/chains"
const pimlicoUrl = "https://api.pimlico.io/v2/base/rpc?apikey=API_KEY"
const pimlicoClient = createPimlicoClient({ transport: http(pimlicoUrl) })
const account = await toSafeSmartAccount({
client: publicClient,
owners: [owner],
version: "1.4.1",
})
// Gas is sponsored, so your user never sees a fee
const smartAccountClient = createSmartAccountClient({
account,
chain: base,
bundlerTransport: http(pimlicoUrl),
paymaster: pimlicoClient,
})
const txHash = await smartAccountClient.sendTransaction({
to: "0x...",
value: parseEther("0.1"),
})Enterprise-grade
What the deal is built on
SLAs and 3am coverage
Contractual uptime SLAs with 24/7/365 monitoring and private-channel support. Your team talks to engineers, not ticket queues.
Compliance your reviewers expect
SOC 2 Type 1 certified, OFAC sanctions screening enforced on every transaction at the infrastructure layer, and paymaster contracts audited by OpenZeppelin and Quantstamp.
The team that wrote the standards
We co-authored ERC-4337, ERC-7677, and ERC-7679 — and the engine behind your deployment has 250M+ production transactions of headroom.
Ecosystems already running the full suite
Ethereum
Base
Arbitrum
Optimism
Polygon
BNB Chain
AvalancheFrequently asked questions
How long does a deployment take?
We onboard new chains continuously, so deployments are routine for us. Bundlers and paymasters typically run on your testnet well before your mainnet date, and your launch timeline drives the schedule.
What do we need to provide?
Reliable RPC access and your chain's details. Pimlico handles the rest, including the smart account contracts your builders depend on. We co-authored ERC-4337, the standard behind them.
What does it cost the builders on our chain?
The same as anywhere else: teams sign up at dashboard.pimlico.io and pay standard usage-based pricing. Ecosystem deals can also include credits or sponsored tiers for your builders, which is part of the conversation.
Do we have to run a gas program too?
No. The infrastructure deployment stands on its own. Ecosystem Gas Programs are the optional growth layer on top, and many chains start with infrastructure and add a funded program once builders arrive.
Are we locked into Pimlico?
No. alto, the bundler under every deployment, is open source with 729K+ downloads, and your builders' permissionless.js code is portable by design. Ecosystems choose the hosted suite for the multi-chain coverage, monitoring, and SLAs on top.
What SLAs and support come with a deployment?
Custom uptime SLAs, 24/7 monitoring by a dedicated team, and private-channel support where your engineers talk to ours.