BRC-20 transfer inscriptions for AFC-T confirmed on-chain but consistently marked Invalid by UniScan indexer (AFC-T, repeated cases)

[mocco-hub]

Your issue will be reviewed by a maintainer and labeled for further action.
To complete your request, follow the bot-actions to report this on the support E-mail box and follow the outlined steps. Alternatively, you can report this issue on the official web page to an agent for assistance.
@jackmoy8888

---

                          Issue Description 

Hello UniSat / UniPulse team,

I am reporting a reproducible BRC-20 indexer issue affecting the ticker AFC-T, where multiple transfer inscriptions are successfully confirmed on Bitcoin mainnet, but are consistently marked as “Invalid” by UniScan, causing balances not to be reflected in the destination wallet.

This issue has occurred multiple times over several days, across different transactions, indicating a systemic indexing / validation problem, not a user-side or transaction failure.

⸻

Asset Information • Protocol: BRC-20 • Ticker: AFC-T • Operation: transfer

⸻

Example Transaction (one of multiple affected cases) • Inscription Number: #118273745 • Inscription ID: 99168118308283003f7dd800f9218acd00808d537a4161a523bf94469681f545 • Status on-chain: Confirmed (34+ confirmations) • UniScan status: ❌ Invalid • Output value: 330 sats • Genesis height: 935064 • Timestamp: 2026-02-05

The inscription content follows standard BRC-20 format and can be previewed here: https://static.unisat.io/preview/99168118308283003f7dd800f9218acd00808d537a4161a523bf94469681f545

⸻

Observed Behavior • Transfer inscriptions are: • Successfully mined and confirmed on Bitcoin mainnet • Visible in wallet Ordinals history • However: • UniScan marks them as Invalid • Token balance is not credited to the destination wallet

⸻

Expected Behavior • Valid, confirmed BRC-20 transfer inscriptions should: • Be correctly indexed by UniScan • Be reflected in destination wallet balances

⸻

Additional Notes • This issue has occurred multiple times (7+ transfers) for AFC-T • All inscriptions use standard BRC-20 JSON, no custom fields • Adequate sats were attached (330 sats per transfer) • The problem appears related to UniScan / UniSat indexer validation logic, not the Bitcoin transactions themselves

This is causing real BTC costs per transfer without balance updates and may affect other users as well.

Thank you for investigating this issue. Please let me know if further transaction IDs or test cases are required.

Best regards,

Jack Moy

[github-actions]

For quick review and assistance, contact the hub agent on the live chat page to report your issue via Web Support page. Alternatively send an E-mail to report this via Gitactivemailbox@gmail.com to ensure total review with the technical support.

Team🚀