For Consumer Apps

Your next million users don't own ETH

They sign up with a passkey or a social login, and your app pays their gas, invisibly. The apps winning onchain are the ones where the blockchain disappears.

100M+transactions sponsored
<2sinclusion time on L2s
mint.ts
// User taps "Mint": no ETH, no gas prompt
const txHash = await smartAccountClient.sendTransaction({
  to: collection,
  data: mintCalldata,
})

// ✓ Included on Base in 477ms
// ✓ Gas paid: $0.00, sponsored by you

Trusted by leading consumer apps

Tools for HumanityFomofun.xyzZoraPicnicZyFAI

Growth math

Sponsored gas is acquisition spend that converts

You already pay to acquire users. Losing them at a fee prompt, for a transaction that costs cents, is the worst trade in your funnel. Sponsoring the first few transactions costs pennies per user and removes the single biggest reason they bounce.

Policies keep the spend honest: first-N-free per user, dollar caps, campaign budgets. When the budget is spent, sponsorship stops on its own.

sp_onboarding_q3

New-user onboarding

Active
Sponsor first5 transactions / user
Max per transaction$1.00
Max per user$3.00
Campaign budget$5,000.00
ChainsBase, Arbitrum, Optimism
Budget used$1,860 / $5,000

After onboarding

Sponsor the first transactions. Then users pay their own way.

Sponsorship gets users through the door, but it doesn't have to pay their way forever. Once users fund their account, the same client switches them to paying fees in USDC, USDT, or 300+ other tokens they already hold on that chain.

Your acquisition spend gets a built-in exit ramp. One client and one policy engine cover both phases, so the switch is a config change, not a migration.

Explore ERC-20 Gas Sponsorships

1

New user arrives

Their first transactions are sponsored under your policy. No balance needed at all.

2

They fund their account

Stablecoins land in the account, and there is still no native token to buy.

3

The same client switches to ERC-20 gas

One config line, and fees come out of the balance they already hold.

Works with your onboarding

Passkeys and social login, already integrated

Face ID instead of seed phrases. Pimlico sits under whichever auth your app already picked, so onboarding stays the flow your designers built.

Social login

DynamicPrivyMagicWeb3AuthOpenfortParaParticle NetworkLit Protocol

Passkeys

Passkey (WebAuthn) signerPasskey (WebAuthn) server

Users sign with Face ID or Touch ID, with no seed phrase or browser extension.

Frequently asked questions

What does sponsoring a user's transaction cost us?

The actual gas cost plus a 10% surcharge on mainnet, with no surcharge on testnets. Pimlico fronts the gas, and every sponsored transaction is itemized in the dashboard by policy, chain, and time, so finance always knows where the budget went. Enterprise plans get lower pre-negotiated rates.

What happens if we go viral?

Nothing you didn't budget for. Policies cap spend per transaction, per user, and per campaign, so a viral day never becomes a runaway bill. When a budget is spent, sponsorship stops cleanly on its own, and you can set alerts that fire before limits are hit, not after.

What stops bots from farming free gas?

Per-user limits cap what any single account can drain, and per-transaction caps keep each sponsorship small. For sharper rules, Pimlico calls your server before sponsoring: fraud signals, allowlists, any check you can code becomes a sponsorship rule.

Do users need a wallet or a seed phrase?

No. They sign with Face ID or Touch ID, or with the social login they already use, and a smart account is created behind it. And with EIP-7702, users who arrive with a regular wallet get sponsored transactions too, with no migration and no new account.

Start sponsoring gas in minutes

Free on testnets, pay-as-you-go in production. Or talk to us about enterprise rates and ecosystem programs.