Most “the board is wrong” posts are not wrong—they’re just unreproducible. Without filter state, refresh timing, and a clear expected/actual, the thread becomes vibes. This is a pre-launch template we want future forum contributors to use.
The goal: make it reproducible in 60 seconds
A good bug report lets another person follow your steps and see the same mismatch. A bad one makes people argue about screenshots. Engineers can fix code; they can’t fix missing information.
Copy-paste template
Title: `[Board] [symptom] — [asset/side] — [rail]`
Body: `Date/time (WAT): […]` → `Page: /board` → `Side: Buy/Sell` → `Asset: USDT/USDC/BTC/ETH` → `Payment keywords: […]` → `Sort: [trust-first?]` → `What I expected: […]` → `What happened: […]` → `Which venue column(s): [Bybit/Bitget/MEXC/LCS]` → `Cross-check: what venue app showed at same moment (short summary)` → `Screenshots: redacted (no NUBAN, no phone, no order ID)`
Redaction rules (please don’t doxx yourself)
- Blur account numbers, phone numbers, emails, and any unique order IDs.
- Avoid posting full counterparty handles—describe trust band instead.
- If you must show a receipt, crop to the minimum necessary.
Common categories that help triage
- Filter mismatch (string mapping changed).
- Refresh drift (board updated vs venue updated).
- Empty column (coverage truth vs bug).
- Limits formatting (min/max displayed oddly).
📚 Internal links
- Payment filter matching — https://ngn.lol/blog/payment-filter-matching-how-board-strings-map-to-ads
- Why board can differ from app — https://ngn.lol/blog/why-p2p-board-can-differ-from-exchange-app
- Redaction house style — https://ngn.lol/blog/forum-redaction-screenshots-evidence-threads-apr-2026
⚖️Disclaimer
Forum template draft. For active orders and money-at-risk issues, use official venue support inside the app.