Limitations & Transparency

Agent Sentinel is a powerful tool — but like any on-chain analysis engine, it's affected by real-world blockchain limitations and edge cases. Here's what you should keep in mind:

🕒 Long Load Times (1–3 minutes)

In some cases, especially with tokens that have high transactional activity, Sentinel can take 1–3 minutes to fully process and return the report.

This is typically due to:

• Network latency from Solana RPCs

• Massive transaction histories

• Metadata parsing failures

• Heavy wallet activity or complex bundling

💡 Hint: To solve this, we've implemented concurrent and parallel executions behind the scenes — so reports are now much faster and more scalable than traditional scanners.

---

🧠 Proprietary Analysis Logic

All reports are powered by our internal ChartGenie analytics engine, which uses custom-built logic to interpret wallet behavior, sniper signals, bonding curves, and market patterns.

This means:

• Sentinel’s insights may differ from those of other scanners or tools

• Every risk score is derived from our unique risk model and heuristics

• Use it as an independent signal, not a replacement for manual review

Eventhough we may differ from original bots, we are fairly sure that our methods are correct. We have backtested and discussed the different methods until satisfaction.

---

🧩 Metadata Gaps

In some cases, token data may be incomplete or missing entirely, which can lead to:

• Partial or broken wallet insights

• Inaccurate holder counts

• Transactional activity not showing up

• “Token not found” errors despite the token being live

This often happens when:

• The token hasn't registered all metadata with Solana

• The mint address is missing key attributes

• The token is too new and RPCs haven’t caught up

We’re constantly improving metadata syncing and expanding coverage — but some edge cases may still occur.

---