Docs / Running it

Deploy

Shipping the front end, and the traps already found.

Vercel

npm run build
vercel deploy --prod

The launchpad address is baked into lib/launchpad.ts, so a deployment with no environment variables at all is a working mainnet front end.

Traps

  • The RPC and the explorer answer 403 to non-browser user agents; server-side fetches have to send a browser one.
  • Vercel variables created as "Sensitive" are not injected into the Next build, so they cannot back a NEXT_PUBLIC_* value.
  • eth_getLogs here caps matches at 10,000 per query. Filter by topic and address, never by block range alone.
  • A raw topics array is silently dropped by viem's getLogs; go through request() when the event ABI is not to hand.