Debug Playbook
Updated: 2026-05-22
Public debugging guidance is intentionally minimal.
Public Triage Order
- Identify failing layer: client, backend API, runtime, chain, or metadata.
- Reproduce once with exact endpoint/route and timestamp.
- Fix one layer at a time and re-test.
- Confirm the game slug used by frontend, backend, runtime, leaderboard, voting, rewards, and NFT sync is the same.
- Confirm local browser/dev-server cache is not serving an old runtime bundle before investigating state bugs.
Public Guardrails
- Do not bypass auth/session checks to "force" success in production.
- Confirm chain-side outcomes before retrying payout/NFT follow-up calls.
- Capture enough telemetry to make incidents reproducible.
- Redact access tokens, refresh tokens, private keys, signatures, RPC API keys, and secret env values.
