Fact-Only Reporting

The principle

Many security and blockchain tools fill gaps with synthetic or example data when real sources are unavailable. That creates a trust problem: analysts cannot tell what is real. Diverg takes the opposite approach: we only show data that comes from live APIs or active testing. When a check cannot be run (e.g. no API key, or target unreachable), we say so clearly instead of substituting fake results.

What you see in reports

Every Diverg report explicitly distinguishes:

• Verified findings: Data from configured APIs and completed tests, with evidence (e.g. request/response, screenshot, or chain link).
• Skipped checks: Tests that were not run, for example because an API key was missing or the target did not support that check. The report states which checks were skipped and why.
• Tool limitations: Known constraints (e.g. rate limits, unsupported chain) that may affect coverage.

Graceful degradation

If you run Diverg without Solscan Pro or Arkham keys, blockchain analysis still runs with the data we can get (e.g. public RPC and block explorers). The report will indicate that entity labels or advanced flow data were skipped. You can then add keys later and re-run, or supplement manually. We never fill those gaps with made-up data.

Why it matters

For incident response, due diligence, or compliance, stakeholders need to rely on every line of a report. Fact-only reporting ensures that when Diverg says "we found X," you can trust that X is real, and when we say "we skipped Y," you know exactly what to double-check or add later.