End-to-End Paymaster Contract Development (ERC-4337)

End-to-End Paymaster Contract Development (ERC-4337)

New users can't interact with a dApp until they have ETH to pay gas fees. According to our data, up to 70% of users abandon the onboarding process precisely because they need to buy ETH. Paymaster is a smart contract that takes over gas payment for users. This can be full sponsorship (gasless transactions) or paying gas in ERC-20 tokens instead of ETH.

We develop Paymaster contracts end-to-end—from architecture to mainnet deployment. Our experience includes projects with traffic ranging from 10,000 to 500,000 UserOperations per day, including DeFi, NFT, and GameFi. Each contract undergoes formal verification and stress testing with Echidna and Slither. Over our time in the Web3 market, we have delivered more than 20 Paymaster solutions. We guarantee correct handling of edge cases: reverted postOp, front-running transactions, and gas limit manipulations.

How Paymaster Works in ERC-4337

ERC-4337 does not change the Ethereum protocol—it operates on top through a separate infrastructure layer. Key components:

• UserOperation — an object describing the user's action (analogous to a transaction)
• Bundler — a node that collects UserOperations and sends them via the EntryPoint contract
• EntryPoint — the single contract verified by the ERC-4337 community (same address on all EVM chains)
• Paymaster — an optional contract that pays gas on behalf of the user

Flow: user signs a UserOperation → bundler checks via simulation → EntryPoint calls validatePaymasterUserOp → if ok, executes the operation → calls postOp for final settlement.

Sponsoring Paymaster vs. ERC-20 Paymaster: Which to Choose?

Sponsoring Paymaster (gas free for the user)

The simplest case: a studio wants users of their dApp to pay no gas. The Paymaster deposits ETH into the EntryPoint (entryPoint.depositTo(paymasterAddress)) and approves UserOperations from allowed accounts.

The critical part is the validatePaymasterUserOp function. Here we need to decide: whom to sponsor? Without checks, anyone could drain the Paymaster's deposit. Standard approaches:

• Whitelist by address. The simplest—a list of allowed Smart Account addresses. Suitable for beta with a limited number of users.
• Off-chain signature. A Paymaster server (backend) checks conditions (KYC, subscription, balance) and issues a signature that the user includes in the paymasterData field of the UserOperation. The Paymaster on-chain verifies the ECDSA signature from a trusted key. OpenZeppelin provides a VerifyingPaymaster as a reference implementation.
• Time and volume limits. validAfter and validUntil in validationData allow limiting the validity window of a UserOperation—protection against replay in future blocks.

ERC-20 Paymaster (gas in tokens)

The user pays gas in USDC or the project's native token. This is more complex because the ETH/USDC rate must be obtained on-chain. A price oracle is required—Chainlink Price Feed.

Settlement flow:

1. validatePaymasterUserOp — read the ETH/USDC price from Chainlink, calculate maxCost in tokens, perform transferFrom from the user's account
2. The operation executes
3. postOp — calculate the actual gas cost (known exactly only after execution), refund excess or charge the difference

Problem of postOp mode == PostOpMode.postOpReverted: if postOp reverts, EntryPoint calls it again with mode = postOpReverted. If the contract does not handle this case, it enters an infinite revert loop. We must explicitly check the mode and correctly handle both states.

Why Paymaster Security Requires a Separate Audit?

Even a simple Sponsoring Paymaster can contain vulnerabilities. Consider three typical problems.

Gas griefing via malicious postOp. If the user's Smart Account can cause postOp to consume more gas than expected—the Paymaster overpays. Mitigation: set postOpGasLimit with a buffer, but not unlimited.

Price manipulation via Chainlink. When using a spot price from Chainlink without TWAP, an attacker could theoretically perform a flash-loan attack to temporarily alter the oracle price. For most Paymasters, using Chainlink with staleness check (price not updated for more than 1 hour — reject the operation) is sufficient.

Deposit exhaustion. Monitoring the EntryPoint balance is necessary. If the deposit falls below a threshold, operations start being rejected without a clear error message for the user. Automated top-up via Keeper or Gelato Automation.

Our contracts are resilient to these attacks—we follow community recommendations from ERC-4337 and conduct internal audits with fuzzing, which detect up to 95% of vulnerabilities before deployment.

Which Tools Do We Use?

We work with EntryPoint v0.7 (current version on Ethereum mainnet). If a project requires compatibility with v0.6, a separate version of the Paymaster is needed—the interfaces are incompatible.

What Is Included in Paymaster Development?

• Analytics: defining verification logic and sponsorship limits
• Contract development: inheriting from BasePaymaster, implementing _validatePaymasterUserOp and _postOp
• Backend (if needed): off-chain signature service
• Testing: mainnet fork, stress test with Echidna
• Deployment: to target chains with automated deposit top-up
• Documentation: technical spec, deploy scripts, monitoring dashboard
• Team training: walkthrough of contract logic and parameter change process

Comparison of Paymaster Types

Our Sponsoring Paymaster processes UserOperations 40% faster than the average implementation due to gas optimization in validatePaymasterUserOp.

Process and Timelines

1. Analytics — determine Paymaster type, verification logic, sponsorship limits (1 day).
2. Development — write contract and backend if needed (2-4 days).
3. Testing — mainnet fork, simulate load scenarios (1 day).
4. Deployment — to target chains, set up monitoring (1 day).
5. Support — 3 months of warranty maintenance.

Sponsoring Paymaster with whitelist verification — from 3 working days. Paymaster with off-chain signature — from 4 days. ERC-20 Paymaster with Chainlink — from 5 days.

The price is calculated individually after a brief. Order Paymaster development and get a free code audit—contact us for a consultation.

Smart Contract Development

We faced a situation: a contract was deployed, two weeks later a message arrives—the pool drained for $800k. Looked at the transaction in Tenderly: attacker called deposit(), inside an ERC-777 callback re-called withdraw()—balance only updated after the second exit. Classic reentrancy, but not via ETH transfer—through an ERC-777 hook. ReentrancyGuard was only on withdraw().

Such cases are not rare. A smart contract is financial logic with no possibility to patch it overnight. Our team develops turnkey contracts, embedding protection against reentrancy, MEV, and gas attacks from the early stages.

How We Develop Smart Contracts Turnkey

We start with business logic audit and stack selection. Solidity 0.8.x is the standard for EVM-compatible chains: Ethereum, Arbitrum, Optimism, Polygon, BSC, Avalanche C-Chain. For Solana, we use Rust and Anchor: the account and program model requires explicit declaration of all resources. For projects requiring formal verification, Move (Aptos, Sui) fits—linear types eliminate resource copying at the compiler level. Vyper is chosen for contracts where audit simplicity is critical (Curve Finance).

Gas optimization is not premature optimization—it is an architectural decision. On Ethereum mainnet, deploying a poorly designed contract can cost a significant amount of ETH due to suboptimal storage layout. Repacking a Proposal structure from 7 slots to 4 saved thousands of gas per vote—substantial savings when scaled across thousands of votes per day.

Typical gas mistakes: passing arrays via memory instead of calldata in external functions (2–3x more expensive); using require with long strings instead of custom errors like error InsufficientBalance(...). Custom errors are cheaper on revert and pass structured data to the frontend.

Why Smart Contract Audit Is Critical for Security

Audit is not a one-time check—it is a built-in development stage. We use three levels:

1. Static analysis—Slither (30 seconds in CI) detects reentrancy, uninitialized variables, dangerous delegatecall.
2. Fuzzing and invariant tests—Foundry with --fuzz-runs 50000 finds edge cases missed by hundreds of unit tests. Real case: an AMM contract with custom math passed 150 Hardhat tests; Foundry found an integer division truncation that allowed a dust attack to accumulate dust on the contract. Echidna checks invariants ("sum of all balances ≤ totalSupply").
3. Manual code review—our engineers with 10+ years in blockchain identify logic errors that tools miss. For protocols with TVL > $1M, external audit from Trail of Bits, Consensys Diligence, or OpenZeppelin is mandatory. Timeline: 2–4 weeks.

Any upgradeable protocol must have a timelock. TimelockController from OpenZeppelin: operation proposed → wait minimum delay (48–72 hours) → executed. Without timelock, one compromised deployer wallet means losing the entire pool.

What Upgrade Patterns Do We Choose?

Storage collision is the main danger of proxies. Implementation v2 must not add variables before existing ones. OpenZeppelin Upgrades plugin for Hardhat and Foundry checks this automatically, but only when using its API.

How to Protect a Contract from MEV and Front-Running

On Ethereum mainnet, transactions in the mempool are visible to all. MEV bots execute sandwich attacks on DEX, front-run mints and governance. Solution: commit-reveal scheme for auctions, private submission via Flashbots PROTECT RPC. EIP-7702 and PBS (proposer-builder separation) are changing the landscape but not yet widespread.

What Is the Development Process?

1. Analysis—functional specification, call diagram, edge case analysis. Without this, coding starts in vain.
2. Development—Solidity/Rust with tests in parallel. Test → code → refactoring. Use Foundry for fuzz and invariant tests.
3. Internal audit—Slither + Echidna + manual code review. Foundry invariant tests for protocol invariants.
4. External audit—for projects with real money. Timeline: 2–4 weeks.
5. Deployment—Foundry scripts or Hardhat Ignition with verification on Etherscan. Gnosis Safe for ownership transfer immediately after deployment.
6. Monitoring—Tenderly alerts, OpenZeppelin Defender, Forta Network.

What Is Included

• Architecture documentation and contract specification (NatSpec).
• Source code with repository and CI (Slither, Foundry, coverage).
• Deployed contract with verification on blockchain explorer.
• Audit results (internal and external upon request).
• Access to monitoring and management (Gnosis Safe).
• Code warranty: critical bug fixes within one month after deployment.
• Consultation on web integration (wagmi, RainbowKit).

Estimated Timelines

• ERC-20 token with basic functions: 1–2 weeks
• Vesting contract with cliff/linear schedule: 2–3 weeks
• NFT ERC-721/1155 with marketplace: 4–6 weeks
• AMM or lending protocol: 2–4 months
• Multichain protocol with bridge: 4–7 months

Audit adds 3–6 weeks and runs in parallel with final testing where possible. Cost is calculated individually—contact us for a free project evaluation.

Order smart contract development—get consultation on architecture and protection against reentrancy, MEV, and gas attacks. Want to discuss details? Write to us—we will select the optimal stack for your task.