Debug Playbook

Updated: 2026-05-22

Public debugging guidance is intentionally minimal.

Public Triage Order

  1. Identify failing layer: client, backend API, runtime, chain, or metadata.
  2. Reproduce once with exact endpoint/route and timestamp.
  3. Fix one layer at a time and re-test.
  4. Confirm the game slug used by frontend, backend, runtime, leaderboard, voting, rewards, and NFT sync is the same.
  5. Confirm local browser/dev-server cache is not serving an old runtime bundle before investigating state bugs.

Public Guardrails

  1. Do not bypass auth/session checks to "force" success in production.
  2. Confirm chain-side outcomes before retrying payout/NFT follow-up calls.
  3. Capture enough telemetry to make incidents reproducible.
  4. Redact access tokens, refresh tokens, private keys, signatures, RPC API keys, and secret env values.