TRANSPARENCY / EVIDENCE / CORRECTIONS

What we know.
What we don't.

Scout records market observations and their limitations. It does not assert that wallet funding overlap proves common ownership, nor that observed price changes are executable returns.

Evidence states

Historical source observation

Timestamped GeckoTerminal quotes and legacy SAGE scores may be incomplete. A provider quote and its SHA-256 digest do not independently authenticate the chain event time or executable trade price.

Verified live event

Requires enabled per-venue decoders, independent reconciliation, actor attribution, finality handling, measured latency and documented coverage. Not independently certified or enabled for public venue-wide wallet intelligence in the current V3 observational pilot.

Unique-wallet counts

A distinct on-chain address is not a distinct person. Router, relayer, MEV and ambiguous ownership records must not become adjusted unique-wallet counts without supporting transaction evidence.

Price high

Max observed source quote is not a peak return or proof of entry and exit. Qualified price evidence additionally needs trade notional, reliable liquidity, coverage and freshness checks.

Liquidity change

A reported reserve decline is not automatically a malicious rug or liquidity-provider withdrawal. An LP-removal claim needs confirmed protocol-specific events.

Wallet connections

Funding overlap and transaction patterns are neutral observations, not a determination of beneficial ownership, collusion or criminal intent.

Methodology versions and corrections

The publicly accessible V3 pilot includes historical Base detections, bounded Base RPC swap observations, and source-reported Solana pool discovery snapshots. Solana RPC pilot swaps have not been independently validated and its counters must not be presented as trading signals. GeckoTerminal Solana prices/volumes/buyers/sellers come from a third-party feed, are partial, can be stale, and do not prove market-wide coverage, wallet ownership, token legitimacy, or executable trade returns. Legacy historical scores reflect their original SAGE version and should not be compared mechanically with future calibrated V3 scores. Source coverage, skipped intervals and data-quality limitations are recorded as unknown, not zero.

Dispute an observation or request a correction by writing to hello@peregrineintel.co with the token contract, pool address, event timestamp, and supporting transaction references. Corrections must preserve the original observation and append the reason, not silently rewrite evidence.

Public research records are not investment recommendations, independent contract audits or substantiated claims about token issuers or wallet owners.