Tutorial: Providing your customers with a gasless experience

[qbzzt]

Description

It is easy to create a private key and an address; it's just a matter of running the right software. But there are many places in the world where getting the ETH to send transactions is much harder. In this tutorial you learn how to cover the onchain gas costs for executing user-signed, off-chain structured data in your smart contract. You have the user sign a structure containing the transaction information, which your offchain code then submits to the blockchain as a transaction.

Preview link

https://deploy-preview-17575.ethereum.it/developers/tutorials/gasless

Related Issue

• Closes Tutorial: Using EIP-712 #14191
• Closes Tutorial: Providing your customers with a gasless experience #17264

[netlify]

✅ Deploy Preview for ethereumorg ready!

Name	Link
🔨 Latest commit	a58fab2
🔍 Latest deploy log	https://app.netlify.com/projects/ethereumorg/deploys/69a13b4cc84ab100073710aa
😎 Deploy Preview	https://deploy-preview-17575.ethereum.it
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	7 paths audited Performance: 56 (🔴 down 4 from production) Accessibility: 94 (🟢 up 1 from production) Best Practices: 100 (no change from production) SEO: 100 (🟢 up 1 from production) PWA: 59 (no change from production) View the detailed breakdown and full score reports

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[mnelsonBT]

Thanks @qbzzt , added 3 suggestions!
@wackerow can we move this one forward when you are able to review?

[myelinated-wackerow]

Status: Reviewed by @mnelsonBT with 3 suggestions (appears addressed).

Well-structured tutorial with honest vulnerability coverage — solid work from a trusted contributor.

Items I'll patch shortly

1. Line 33: github clone → git clone (typo)
2. Line 48: "the block time om Sepolia" → "on Sepolia" (typo)
3. Line 8: Updating published to 2026-02-27
4. Line 5: Adding tags — suggesting ["gasless", "solidity", "eip-712", "meta-transactions"]
5. Line 6: skill: beginner → skill: intermediate — this covers EIP-712 signing, ecrecover, and relay server architecture

Requests for the author (@qbzzt)

6. contractAddr / chainId / signTypedDataAsync (around line 137) — these appear in the code walkthrough without context on where they come from. A brief note on the WAGMI hooks that provide them would help.
7. EIP-712 not named until deep in the code — a one-liner in the introduction (e.g., "This tutorial uses EIP-712 typed structured data signing...") would set expectations early.
8. No prerequisites section — a brief note on assumed knowledge (Solidity, React, WAGMI) would help readers self-select.

Verdict

Technically sound, nothing blocking. All issues are minor — typos and polish. Items 1–5 will be patched directly; 6–8 are suggestions for the author's consideration.

Reviewed by Claude (claude-opus-4-6)

[qbzzt]

• contractAddr / chainId / signTypedDataAsync (around line 137) — these appear in the code walkthrough without context on where they come from. A brief note on the WAGMI hooks that provide them would help.
• EIP-712 not named until deep in the code — a one-liner in the introduction (e.g., "This tutorial uses EIP-712 typed structured data signing...") would set expectations early.
• No prerequisites section — a brief note on assumed knowledge (Solidity, React, WAGMI) would help readers self-select.

Sorry, I'll do it later today.

[qbzzt]

• contractAddr / chainId / signTypedDataAsync (around line 137) — these appear in the code walkthrough without context on where they come from. A brief note on the WAGMI hooks that provide them would help.
• EIP-712 not named until deep in the code — a one-liner in the introduction (e.g., "This tutorial uses EIP-712 typed structured data signing...") would set expectations early.
• No prerequisites section — a brief note on assumed knowledge (Solidity, React, WAGMI) would help readers self-select.

Sorry, I'll do it later today.

Done.

[wackerow]

Looks good! Thanks @qbzzt!