Deployment
Current state: local only. The app has not been deployed. openpons.xyz is not
connected, and no OPONS token exists.
Local
npm install
npm run build
npm start # production server on http://localhost:4663
Planned: openpons.xyz (not done)
The target is Cloudflare, via the OpenNext adapter for Next.js (@opennextjs/cloudflare). Notes for when this happens:
- Runtime. The API routes use Node APIs only through viem/fetch. The docs pages read
docs/*.mdat build time (generateStaticParams), so they are static. - Caches. The in-process caches (launch index, graduated scan) are per isolate. On Workers, move them to KV or Durable Objects, or accept cold rebuilds. The graduated backfill should become a scheduled job.
- Rate limiting. Replace the in-memory limiter with Cloudflare rate-limiting rules.
- RPC. Add a dedicated RPC via
OPENPONS_RPC_URLS; keep the official RPC as a fallback. - Hosted MCP. Add an HTTP (streamable) transport endpoint that reuses the same tool definitions.
- Metadata.
metadataBaseis alreadyhttps://openpons.xyz, with the canonical URL, OG and Twitter images fromsrc/app/opengraph-image.tsx. - Token. Before announcing $OPONS, set the real CA in
src/config/token.ts— nothing else needs editing.
Pre-launch checklist
- Re-verify the Pons contract codehashes (
src/lib/pons/addresses.ts) against live chain -
npm test && npm run typecheck && npm run build - Manual wallet matrix from WALLET-INTEGRATION.md
- Legal review of the disclaimers (independence, not financial advice)