Paymaster Service Manager

WHAT IT DOES

Paymaster Service Manager gives you direct control over ERC-20 token allowances and paymaster contract deposits on EVM-compatible chains. It reads current allowance values (not just historical approval events), checks paymaster native balances, and lets you approve, revoke, deposit, or withdraw funds with a single signature. The tool also monitors pending user operations in the mempool and references gas price oracles to help you estimate transaction costs before signing. Designed for developers managing paymasters in ERC-4337 smart accounts, it eliminates guesswork by showing you exactly what your wallet has approved and what the paymaster holds right now.

HOW TO USE

Connect your EVM wallet using the built-in bridge. Enter the paymaster contract address you want to manage. Optionally supply a token address for ERC-20 operations—leave it empty for native ETH deposits. Set the spender address to check or modify allowances. Use the "Check allowance" button to see the current approved amount. Click "Approve" to set a new allowance, or "Revoke" to set it to zero. Use "Deposit" to send native or ERC-20 funds to the paymaster, and "Withdraw" to pull native funds back to your wallet. Each action generates a transaction that you review and sign in your wallet. After confirmation, the tool refreshes balances and allowances automatically.

TECHNICAL APPROACH

Unlike tools that rely solely on Approval event logs—which only prove an approval happened at some point, not that it still exists—this tool queries the live allowance() and balanceOf() state directly from the contract. It uses ethers v5.7.2 with a robust error-handling wrapper that extracts nested failure reasons, so you never see "[object Object]" when a transaction fails. When fetching historical logs for mempool analysis, it chunks block ranges and halves them on RPC errors, because public endpoints cap ranges differently and a single refusal should not abort the entire scan. For transaction costing, it reads receipt.effectiveGasPrice post‑EIP‑1559 rather than tx.gasPrice, which overstates spend. Batched operations are awaited sequentially to avoid nonce collisions.

WHAT IT CANNOT SEE

This tool cannot detect off‑chain paymaster policies, intent, or rate limits that your paymaster enforces outside the blockchain. It cannot guarantee transaction inclusion, finality, or mempool propagation—those depend on network conditions and gas markets. It does not simulate execution or test whether your paymaster will accept a given user operation; it only manages allowances and deposits. It cannot see pending operations that are not yet broadcast to the public mempool, nor can it verify whether a paymaster contract implements the specific withdrawal functions you expect.

PLEASE NOTE

This tool supports EVM‑compatible chains only (Ethereum, Goerli, Sepolia, Arbitrum, Optimism, Polygon). Solana, Tron, Starknet, SUI, TON, Aptos, Bitcoin, Cosmos, and XRP are not supported. The tool is read‑write and requires signing transactions—always verify the spender, amount, and recipient before approving. No contract addresses are hardcoded; you paste the contract you are using, so you are responsible for verifying its safety. This tool is free and open under the BotGentz PLAYBOOK‑C specification.