Deploy Paymaster Contract

WHAT IT DOES

Deploy Paymaster Contract enables you to deploy your own paymaster proxy contract using the EIP-1167 minimal proxy pattern. A paymaster is a contract that sponsors gas fees for users in Gas Station Network (GSN) and meta-transaction systems, allowing your dApp to cover transaction costs for your users. The tool reads your connected wallet address to determine the deployer, validates the current chain ID, checks your wallet balance to confirm sufficient native tokens for deployment gas fees, and lets you specify the implementation contract, proxy factory address, optional salt for deterministic addresses, and initialization parameters such as token configuration or fee settings. It then broadcasts a deployment transaction using a factory contract, which creates a minimal proxy pointing to your chosen implementation and optionally initializes it with your provided data. After deployment, the tool displays your new paymaster contract address with a transaction link for verification.

HOW TO USE

Connect your wallet using the BGWallet connector. Select the network you want to deploy on from the dropdown menu. Enter the implementation contract address you want your paymaster to point to—this is the contract that contains the paymaster logic your proxy will delegate calls to. Enter the proxy factory address for your chosen network, which uses the EIP-1167 minimal proxy pattern to create new proxy instances. Optionally, specify a salt value to control the deterministic deployment address—the same salt on the same network with the same implementation will produce the same address. You can also provide initialization data (hex-encoded calldata) to configure your paymaster during deployment, such as setting the token address, fee rates, or allowed recipients. The review panel displays all parameters, your wallet balance, and estimated gas cost. After reviewing, click "Deploy paymaster" to broadcast the transaction. The tool shows progress and displays your deployed paymaster address once confirmed, with a copy button for easy reference.

TECHNICAL MECHANISM

This tool uses a factory contract that implements the EIP-1167 minimal proxy pattern with create2 support for deterministic deployment. When you initiate deployment, the tool validates the implementation and factory addresses, then calls the factory's deploy() function with the implementation address, a salt value, and optional initialization data. The factory creates a new proxy contract using the create2 opcode, which allows for deterministic addresses based on the factory address, implementation address, salt, and initialization data. The proxy contains minimal bytecode that delegates all calls to the implementation contract using delegatecall, with the proxy's own storage persisting independently. The optional initialization data is executed immediately after deployment to configure the paymaster's state. The tool estimates gas using the factory's deploy() function with a 20% buffer to account for network variability. After the transaction is mined, the tool parses the Deployed event from the factory contract to extract the new proxy address, or computes it using create2 address derivation as a fallback. 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 deployed paymaster contract will be accepted or recognized by external relay hubs or meta-transaction systems without additional configuration—you must separately register your paymaster with your chosen relay service. It does not verify the implementation contract's code or safety; you are responsible for ensuring the implementation contract is secure and trusted. The tool cannot recover if the deployment fails due to insufficient gas, network issues, or if the factory contract rejects your deployment parameters. It does not automatically register your deployed paymaster with any relay hub or GSN service. The tool does not verify that your paymaster has sufficient funds to cover sponsored gas costs—you must fund it separately after deployment. It does not support chains where the required implementation or factory addresses are not available, and it does not validate that the provided implementation address is a valid paymaster implementation.

PLEASE NOTE

This tool works only on EVM-compatible chains that support the EIP-1167 minimal proxy pattern with create2 and have a compatible factory contract. You must provide the correct implementation and factory addresses for your chosen network—the tool does not hardcode these addresses. Always verify that the implementation contract you are using is trusted and secure, as your proxy will delegate all calls to it. The deployment transaction will cost gas in native tokens, paid by your connected wallet. Using a salt value allows you to deploy the same paymaster address deterministically across deployments, which can be useful for upgradeability or registration. After deployment, you must fund your paymaster with native tokens to cover sponsored gas costs. The initialization data parameter is optional but may be required by your chosen implementation to set configuration parameters such as allowed tokens or fee structures.