Send Meta Transaction via GSN

WHAT IT DOES

Send Meta Transaction via GSN enables you to execute blockchain transactions without paying gas fees yourself. Instead, the Gas Station Network (GSN) relay hub pays the gas, and you sign a meta-transaction that authorizes the relay to submit your transaction on your behalf. This tool reads your wallet's native token balance, validates the target contract address and calldata, checks the GSN relay hub's balance to ensure it can cover gas costs, and fetches current gas prices and GSN configuration parameters including the paymaster, forwarder, and relay hub addresses. Once you sign, the tool packages your transaction into a GSN relay request, signs it using EIP-712 typed data signing, and broadcasts it to the relay hub. The relay then submits your transaction to the network, paying the gas fees from its own balance.

HOW TO USE

Connect your wallet using the BGWallet connector. Select the network you want to use from the dropdown menu—the tool supports Ethereum, Goerli, Optimism, BNB Chain, Polygon, and Arbitrum. Enter the target contract address you want to interact with. Paste the encoded calldata (hex string without the 0x prefix) for the function you wish to call. Optionally, specify a value in native tokens to send with the meta-transaction. The review panel will display the target contract, calldata length, value, current gas price from the relay, relay hub balance, and your wallet balance. After verifying the details, click "Send meta-transaction" to sign the EIP-712 typed data and broadcast it to the GSN relay hub. The tool will show progress and provide a transaction link once confirmed.

TECHNICAL MECHANISM

This tool integrates with the Gas Station Network by constructing an EIP-712 typed data structure that conforms to the GSN Relay Hub specification. It reads the current chain's relay hub, forwarder, and paymaster addresses from a built-in registry. The tool fetches the current gas price from the provider and estimates a conservative gas limit for the relay call. It then constructs a RelayRequest object containing the target address, value, gas limit, nonce, calldata, gas price, paymaster address, paymaster data, and the sender's address. Using the wallet's signer, it generates an EIP-712 signature over this structured data. The signature is included in a relayCall() transaction to the GSN relay hub, which verifies the signature, deducts the gas cost from the paymaster's balance, and forwards the transaction to the target contract. The tool uses receipt.effectiveGasPrice to display accurate gas costs after the transaction is mined, accounting for post-EIP-1559 networks.

WHAT IT CANNOT SEE

This tool cannot guarantee relay hub availability or response time—if the relay hub is offline or overloaded, your meta-transaction will fail. It does not support all token types for gas payment; gas is paid in native tokens by the relay. If the relay hub rejects your request (e.g., due to signature validation failure, insufficient paymaster balance, or invalid nonce), the tool cannot recover the transaction. It cannot simulate relay transaction success before signing, so you are responsible for verifying the target contract and calldata. The tool does not automatically detect if the relay hub's balance is insufficient before submitting; it only reads the balance for display. It does not support chains without GSN deployment or chains where the relay hub addresses differ from the registry.

PLEASE NOTE

This tool works only on EVM-compatible chains where GSN is deployed, as listed in the built-in registry. Always verify the relay hub, forwarder, and paymaster addresses displayed in the review panel before signing. The tool reads the relay hub balance live, but a low balance may cause your meta-transaction to fail. Ensure your wallet is connected and you have sufficient native token balance to cover any value you are sending, though gas is paid by the relay. For security, the tool never asks for private keys or seed phrases—all signing is handled by your connected wallet extension. Meta-transactions are signed using EIP-712 typed data, which provides human-readable transaction details in supported wallets.