Bundle User Operation

WHAT IT DOES

Bundle User Operation enables you to construct, sign, and submit ERC-4337 user operations to the entry point contract for execution. User operations are the core transaction abstraction primitive in account abstraction—they represent a request from a smart account to execute a call on its behalf, with gas sponsorship and custom validation logic. The tool reads your connected wallet address to determine the sender (smart account), validates the current chain ID, fetches the current nonce for the sender account to prevent replay attacks, and lets you specify all user operation parameters including call data, gas limits, fee settings, optional paymaster, and initialization code. It constructs an EIP-712 typed data structure, signs it with your wallet, and submits the bundled operation to the entry point via the handleOps() function. After submission, the tool displays the transaction hash and status, with a link to the blockchain explorer for verification.

HOW TO USE

Connect your wallet using the BGWallet connector. Select the network you want to use from the dropdown menu. Enter the entry point contract address for your chosen network—this is the core ERC-4337 contract that processes user operations. Enter the sender address (your ERC-4337 smart account) that will execute the operation. Provide the call data (hex-encoded) for the function you want the smart account to execute. Specify gas limits: call gas limit, verification gas limit, and pre-verification gas. Set the fee parameters: max fee per gas and max priority fee per gas (in gwei). Optionally, provide a paymaster address with data for gas sponsorship, or initialization code if this is the first operation for a new smart account. The review panel displays all parameters and fetches the current nonce for your sender account. After reviewing, click "Bundle user operation" to sign and submit. The tool shows progress and displays the user operation hash and status once confirmed.

TECHNICAL MECHANISM

This tool follows the ERC-4337 specification for user operations. It constructs a UserOperation struct containing all required fields: sender, nonce, initCode, callData, callGasLimit, verificationGasLimit, preVerificationGas, maxFeePerGas, maxPriorityFeePerGas, paymasterAndData, and signature. The tool fetches the current nonce for the sender from the entry point's getNonce() function to prevent replay attacks. It then creates an EIP-712 typed data structure following the AccountAbstraction domain specification, with the entry point address as the verifying contract and the current chain ID for replay protection across networks. The user signs this typed data using their wallet's _signTypedData() function, producing a signature that is included in the user operation. The tool estimates gas using the entry point's handleOps() function with a 20% buffer to account for variable execution costs. Finally, it calls handleOps() with an array containing the single user operation, passing the caller's address as the beneficiary for gas refunds. Gas costs are displayed using receipt.effectiveGasPrice for accurate reporting on post-EIP-1559 networks.

WHAT IT CANNOT SEE

This tool cannot guarantee that your user operation will be accepted or included by bundlers or mined within any specific timeframe—bundlers may choose to ignore or delay operations based on their own policies. It does not verify the target contract's code or safety; you are responsible for ensuring the contract you are calling is secure and trusted. The tool cannot recover if the user operation fails during execution at the smart account level—if the validation or execution reverts, the entire operation fails. It does not automatically retry failed operations; you must resubmit manually. The tool does not support all ERC-4337 implementation variations or custom validation logic that may exist in different account implementations. It cannot guarantee paymaster reliability or availability; if the paymaster is out of funds or rejects the operation, it will fail. The tool does not support chains without ERC-4337 entry point contracts or bundler infrastructure, and does not simulate the user operation before submission to verify success.

PLEASE NOTE

This tool works only on EVM-compatible chains that support the ERC-4337 standard and have a deployed entry point contract. You must provide the correct entry point address for your chosen network—the tool does not hardcode these addresses. Always verify that the smart account address you are using is a valid ERC-4337 account. The sender must be a contract that supports the ERC-4337 interface and has been deployed (unless you are using initCode to deploy it atomically). The gas parameters should be set appropriately to ensure the operation executes successfully. Using a paymaster requires a valid paymaster address and correctly formatted data. The tool uses EIP-712 typed data signing, which provides human-readable transaction details in supported wallets. After submission, you may need to wait for bundlers to include your operation in a bundle and for miners to confirm it.