A sponsored or relayed transaction flow in which someone other than the sender initially pays network gas. It may let a user avoid holding the native token, but it does not remove fees, signature risk, approvals, price or slippage risk, or the possibility of failed execution.
Supports: ERC-2771 defines relayed meta-transactions, the recipient's trusted-forwarder check, and the risk of a malicious or upgradeable forwarder forging the effective sender.
Supports: ERC-4337 defines UserOperations, bundlers, paymasters, nonce and chain-bound signature requirements, and sponsored or token-fee use cases without prescribing a universal fee conversion or sponsor policy.
Gasless means another party initially pays gas; it does not mean the trade, authorization, or execution is free of risk.
ERC-2771 relies on a recipient's trusted forwarder; ERC-4337 uses UserOperations and can use a paymaster.
Review the exact chain, contracts, calldata, nonce, expiry, sponsor, fee, assets, recipient, and allowances before signing.
A sponsor or paymaster can reject a request, and relaying does not guarantee price, route, MEV protection, or settlement.
A wallet prepares a UserOperation for a swap and states that a named paymaster is requested to sponsor gas. Before signing, the user checks the chain, EntryPoint, target contract, token amounts, minimum receive amount, recipient, expiry, allowance, and displayed fee policy. If any of those fields or the paymaster changes, the user treats it as a new authorization rather than accepting the old prompt.
A design in which a user signs constraints for a desired outcome and a protocol or solver attempts settlement. A signed intent is an authorization with a specific trust and replay boundary, not a guarantee of price, route, MEV protection, or successful settlement.
A network-specific transaction-execution charge. On Ethereum, the fee depends on gas used and the transaction's effective gas price; a wallet estimate is not a guarantee of execution, final outcome, or total cost on another network.
A protocol layer that executes transactions outside an L1 while using that L1 for some combination of data availability, proofs, dispute resolution, or settlement. Fees, finality, bridges, and withdrawal paths depend on the specific L2 design.
A wallet application and browser/mobile interface for managing accounts and interacting with supported networks and dapps. Connecting a site, signing a message, approving token spending, and sending a transaction are separate requests with different effects.
Explore all our strategic guides about Blockchain to take your operations to the next level.
View all articles