What problem does it solve?
Deploying Ethereum frontend applications built with Scaffold-ETH and Next.js to production involves many subtle, easy-to-miss pitfalls: local fork vs empty chain testing, static export quirks on IPFS, Node 25+ localStorage polyfills, route 404s caused by missing trailing slashes, stale CI builds, and correct ENS content-hash configuration. This playbook collects the proven build steps, verification checks, and deployment options so teams avoid common failures and ship predictable releases.
Core Features & Use Cases
- Fork-mode development: Use real-chain state via anvil forks so frontend integration tests run against real tokens, liquidity, and contract state instead of empty local chains.
- IPFS-safe static export: Clean-build guidance, localStorage polyfill, trailingSlash configuration, CID verification, and routing checks to ensure every route serves an index.html on IPFS.
- Vercel & ENS guidance: Monorepo Vercel settings, prebuilt workflow alternatives, and the two-transaction ENS subdomain flow with verification steps.
- Production checklist and QA: End-to-end build verification, OG image and metadata validation, onchain content-hash checks, and browser UX test steps for wallet flows.
- Use case: Ship a Scaffold-ETH dApp from forked local testing to a verified myapp.yourname.eth.link IPFS deployment with ENS content-hash set and QA signoff.
Quick Start
Prepare your Scaffold-ETH Next.js project for production by enabling fork-mode testing, building an IPFS-safe static export with trailingSlash and a localStorage polyfill, uploading the out/ folder to IPFS, saving the new CID, and setting that CID as the ENS subdomain content hash.