Why this was rebuilt. The original report included rows where the linked TX did not match the customer's narrative, and grouped non-indexing tickets (bank withdrawals, scam tokens, wrong-network deposits, card refunds, off-platform PnL) as indexing issues. This rebuild applies a strict filter: customer reported missing or delayed asset, TX confirmed on-chain at the customer's fomo address, narrative matches TX, no alternative cause identified. The 85 candidates that did not pass are categorized at the bottom under Excluded for transparency.
Verified indexing failures
12
Display sync delays (self-resolved)
10
Excluded (not indexing)
~85
All verified (22)
Tier 1: Confirmed indexing (12)
Tier 2: Display sync delays (10)
Excluded — not indexing (~85)
Showing 22 of 22
Conversation▲▼
Username▲▼
Tier▲▼
Type▲▼
Network▲▼
TX
Issue
Root cause / outcome
Tickets that are NOT indexing issues
Categories engineering does not need to investigate. These were filtered out of the verified set. Counts represent how many of the 120 candidates fell into each bucket.
Category
Count
Why excluded
What changed from the original report
Scope correction. Original report claimed "Solana only" but included ETH, ARB, and other off-platform networks. This rebuild keeps Base outage cases (real indexing failures on a fomo-supported network) and explicitly excludes wrong-network deposits.
TX-to-narrative verification. Each row was verified against its linked TX. Rows where the TX was unrelated to the customer's claim (tradesbread, boogie5657, RearReadyTuna, etc.) were reclassified or excluded.
Root cause attribution. Each Tier 1 entry documents the actual cause where identifiable (routing partner authority wallet change, Crossmint first-transaction flow, Base outage recovery sweep, manual indexing required).
Crossmint fix context. Engineering deployed a Crossmint indexing fix on Jun 25, 2026. Cases tagged Crossmint occurred before or around that fix and should be checked to confirm coverage.
Excluded categories surfaced. The 85 non-indexing candidates are categorized so engineering can see what was filtered and why, instead of wading through them.