Ecosystem Gas Programs
Grow your chain by removing its biggest barrier
The hardest step for every app on your chain is the same: users need native token before they can do anything. Fund a gas program and that step disappears for every builder at once.
Your ecosystem funds a program
A single budget, with rules for which apps and users qualify.
Pimlico distributes it as sponsored gas
Approved apps sponsor transactions through their existing integration.
Users transact with zero native tokens
Onboarding friction disappears across your whole ecosystem at once.
You measure the growth
Per-app dashboards tie every dollar of gas to transactions and active users.
Teams like these already run on Pimlico
Approved apps join your program through the integration they already have.
Why chains run programs
Native-token onboarding is your ecosystem's shared bottleneck
Every app on your chain pays the same friction tax. Solving it once, at the ecosystem level, lifts all of them.
Activation, not airdrops
Gas programs subsidize real usage, the transactions that happen in real apps, instead of token giveaways that get farmed and dumped.
A builder magnet
"Deploy here and your users' gas is covered" is one of the strongest BD offers a chain can make.
Controlled spend
The full sponsorship policy engine applies: per-app budgets, per-user caps, time windows. The program ends when you say it does.
Controlled spend
The program ends when you say it does
Your program is a budget enforced at the infrastructure layer. Every sponsorship is checked against your rules before it happens: per app, per user, per transaction, and against the program budget as a whole.
Change a limit in the dashboard and it applies to the very next transaction. Spend is itemized per app and per policy, so your foundation knows exactly what the budget bought.
sp_onboarding_q3
New-user onboarding
The builders you attract
Your chain becomes a one-line config change
A gas program is a builder magnet because the builders are already here. The largest smart account developer community ships on Pimlico's open-source stack, and pointing it at your chain is a config change, not a migration.
We also co-authored the standards everyone builds on: ERC-4337, ERC-7677 and ERC-7679.
For your builders
Enrollment is one line
Approved teams attach your program's policy ID to the transactions they already send through Pimlico. No new contracts to deploy, no tokens to distribute, no integration project to ask of them.
That is what makes "deploy here and your users' gas is covered" an offer builders accept on the spot: saying yes costs them one line.
// Attach a sponsorship policy created in the dashboard:
// "Sponsor the first 5 transactions per user, up to $1 each,
// with a $5,000 campaign budget"
const txHash = await smartAccountClient.sendTransaction({
to: "0x...",
data: "0x...",
paymasterContext: {
sponsorshipPolicyId: "sp_first_five_free",
},
})Partnership
Launching a chain? We move fast.
We are live on 100+ chains and onboard new ones continuously. If you are launching an L2, an L3, or an appchain, we can have bundlers and paymasters running before your mainnet does.
Ecosystem deals are bespoke (budgets, eligibility, co-marketing), so the right first step is a conversation.
What partners get
- Bundler and paymaster live on your chain, including pre-mainnet
- Day-one smart account support for every team building on you
- A funded gas program designed around your growth targets
- Co-marketing to the largest smart account developer base
Ecosystems already running the full suite
Due diligence
Infrastructure your foundation can underwrite
Frequently asked questions
Who funds the gas in an ecosystem program?
The chain or ecosystem foundation funds a program budget; Pimlico distributes it as sponsored gas across the apps you choose to support, with per-app and per-user controls so the budget drives the activity you actually want.
How do developers on our chain enroll?
You define the eligibility criteria; approved teams get sponsorship through their existing Pimlico integration, with no extra contracts to deploy or tokens to distribute.
What visibility do we get?
Program dashboards show spend, transactions, active users, and per-app breakdowns, so you can measure exactly what the program generates.
Our chain is new. Can Pimlico support it?
Almost certainly. We are live on 100+ chains and onboard new ones continuously, and partnering with upcoming chains early is something we actively look for.