Skip to main content

How to Build a Gasless Web3 App

Building a gasless Web3 app requires:
Biconomy’s MEE provides all the functionality of traditional ERC-4337 bundlers and paymasters in a unified, easier-to-use package. Instead of configuring separate bundler and paymaster services, MEE handles everything automatically.
You’ll also need:
  • A Biconomy dashboard account for API keys
  • A sponsorship policy (who/what to sponsor)
  • Frontend integration (React, Vue, vanilla JS, etc.)
Step 1: Install dependencies
Step 2: Get API keys from Biconomy Dashboard
  1. Go to dashboard.biconomy.io
  2. Create a new project
  3. Get your MEE API key
  4. Configure sponsorship policies
Step 3: Initialize the SDK with MEE
MEE (Modular Execution Environment) replaces the need to configure separate bundlers and paymasters. It provides all ERC-4337 functionality plus cross-chain capabilities in a single, unified interface.
Once configured, sending gasless transactions is simple with MEE:
For contract interactions:
MEE automatically handles gas sponsorship based on your dashboard configuration.
Sponsorship policies control who and what gets sponsored. Configure in the Biconomy Dashboard:Dashboard Configuration:
  1. Navigate to MEE sponsorship settings
  2. Set spending limits (per transaction, total)
MEE handles gas sponsorship (traditionally done by ERC-4337 paymasters) as part of its unified execution environment. You configure policies in the dashboard, and MEE applies them automatically.
Policy Examples:Sponsor all transactions (development):
Sponsor with spending limits:
For first-time users, the smart account needs to be deployed. MEE handles this automatically:
Best practices for onboarding:
Batch operations save gas and improve UX with MEE:
Real-world example - NFT mint with approval:
Even for gasless transactions, showing users what’s happening builds trust:
UI Example:
Common errors and how to handle them:
Implement retry logic:
Here’s a complete gasless NFT minting app using MEE:
MEE provides all the functionality of traditional ERC-4337 bundlers and paymasters in a single, unified interface. No need to configure separate bundler URLs or paymaster URLs.

Continue building

ERC-4337 Paymaster

Deep dive into paymaster configuration

Batched Transactions

Combine multiple operations efficiently