Simple Base SwapSimple Base SwapOpen app
← All articles
Nov 14, 2026·5 min read

Meta Transactions and Relayers: The Gasless Pattern Before Account Abstraction

basegassmart-contractsguidesbeginners
base

Our paymasters guide covers how ERC-4337 smart wallets let an app sponsor your gas fee. That system is relatively new, and it depends on you using a smart contract wallet. For years before it existed, and still today on plenty of apps, developers reached the same goal, letting a user transact without holding ETH, through a different mechanism entirely: meta transactions relayed by a trusted forwarder. If you have ever signed something in an app that said no gas needed without your wallet looking or behaving like a smart wallet, there is a decent chance this older pattern was behind it.

What a meta transaction actually is

A regular transaction on Base is something your wallet signs and sends directly to the network, with the gas fee paid from that same wallet's ETH balance. A meta transaction splits that in two. You sign a message describing what you want to do, but you never broadcast it yourself. Instead, that signed message gets handed to a separate party, usually called a relayer, which wraps it inside its own real transaction and pays the gas to submit it. The contract on the receiving end checks your signature and treats the action as if it came from you, because in every meaningful sense it did. You authorized it. You just did not pay for the trip.

This is defined at the smart contract level by a standard called ERC2771, which describes how a contract can safely recognize that a call arrived through a forwarder rather than directly from a wallet, and still correctly identify the original signer as the real sender of the action. A widely used implementation of this pattern comes from OpenZeppelin's ERC2771Context, which many contracts on Base and other EVM networks build on when they want to support this flow.

The trusted forwarder's job

The forwarder is a small, specific contract that sits between the relayer and the app's actual contract. Its only job is to verify that a signed request is genuine and has not already been used, usually by checking a nonce, and then pass the call through to the destination contract while preserving who the original signer was. The word trusted matters here. The app's contract has to explicitly list which forwarder address it will accept calls from. A forwarder it does not recognize cannot impersonate a user, no matter what it submits, because the receiving contract simply will not treat an unlisted forwarder's calls as coming from anyone at all.

Where relayer networks fit in

Someone still has to run the relayer that pays the gas and submits these wrapped transactions. Early implementations of this idea, often grouped under the name Gas Station Network, built shared relayer infrastructure that multiple apps could plug into rather than each one running its own. Commercial relay services such as Gelato and Biconomy later built on and around the same ERC2771 interface, giving app developers a way to sponsor gas for their users without operating relayer servers themselves. From a user's side, none of this is visible. You see a transaction that did not ask you to hold ETH first, and the relaying happens entirely behind the app's interface.

How this compares to account abstraction

The paymaster system covered in our ERC4337 guide and this meta transaction pattern solve the same user problem, not needing ETH to act, but through different plumbing. A paymaster requires your wallet itself to be a smart contract that can route a UserOperation through a bundler and an EntryPoint contract. Meta transactions ask nothing of your wallet. Any regular wallet, including a standard self custody wallet with a single private key, can sign the message a relayer needs, because signing a message costs nothing regardless of wallet type. That is a meaningful practical difference: meta transactions can bring gasless actions to wallets that never adopt smart contract features at all, while a paymaster only works once a wallet has made that upgrade.

What changes for you as a wallet holder

Functionally, very little. You are still signing something, and that signature still authorizes a real, final action once the relayer submits it. The same habits from our wallet signature requests article apply without exception: read what you are signing, understand what action it triggers, and do not assume that because no gas fee is shown, nothing meaningful is happening. A gasless signature can still move funds, grant an approval, or change account state exactly like a transaction can. The absence of a fee is a convenience the app built, not a sign that the action itself is low stakes.

The risk worth knowing about

The honest tradeoff is centralization around the relayer. If the relayer an app depends on goes offline, runs out of funds to sponsor gas, or chooses to stop forwarding certain requests, your signed message simply does not get submitted until something changes. That is an availability risk rather than a security risk to your funds, since the forwarder contract still only executes what you actually signed, but it is worth knowing that a gasless app's uptime depends on infrastructure you cannot see or control from your wallet.

The short version

Meta transactions let you sign an action and have a relayer pay the gas to submit it, verified on chain by a trusted forwarder contract under the ERC2771 standard. It predates account abstraction, works with any wallet rather than only smart contract wallets, and shifts the same signing diligence onto a message instead of a transaction. If you would rather hold a straightforward wallet where every action you take is a transaction you can see and pay for yourself, Simple Base Swap is a self custody wallet built for exactly one network. Start at app.simplebaseswap.com, or grab the iOS or Android app.

Ready to try it yourself?

Create a non-custodial wallet on Base in seconds. No account, no sign-up.

Open the web app