10 · docs/DEPLOYMENT.mdOpenPons manual

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:

  1. Runtime. The API routes use Node APIs only through viem/fetch. The docs pages read docs/*.md at build time (generateStaticParams), so they are static.
  2. 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.
  3. Rate limiting. Replace the in-memory limiter with Cloudflare rate-limiting rules.
  4. RPC. Add a dedicated RPC via OPENPONS_RPC_URLS; keep the official RPC as a fallback.
  5. Hosted MCP. Add an HTTP (streamable) transport endpoint that reuses the same tool definitions.
  6. Metadata. metadataBase is already https://openpons.xyz, with the canonical URL, OG and Twitter images from src/app/opengraph-image.tsx.
  7. 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)
Independent · not affiliated with Pons or Robinhood@openpons