Data Sources

ScytheRadar holds one standard: every number must be challengeable on-chain. Below are the data sources we use — all of them public, with no unverifiable black box.

1. On-chain data (RPC nodes)

We read real on-chain state through multi-chain RPC nodes, covering four chains:

We use multi-node redundancy plus cross-validation to avoid single-node failures or anomalous responses.

2. Contract security scanning (GoPlus)

Honeypot, mintability, ownership reclaim, abnormal trading tax, holder concentration and other security checks come from the public security API of GoPlus Security (api.gopluslabs.io).

3. Market data & liquidity

• DexScreener: token price, 24h volume, liquidity pool (LP) data.
• GeckoTerminal: supplementary price and liquidity data (used for cross-checking).

4. Deploy-time verification (blastapi archive)

Contract deploy time is recovered by replaying historical block state through blastapi archive nodes. To avoid the "fake archive" problem (some free nodes silently return current state for historical queries and forge a date), we apply a triple anti-forgery check: a reference contract (e.g. USDT/WETH) must have code at the target block, which proves the archive is genuine.

5. Market scan baseline library

The "new-pair baseline library" on the Market Radar page comes from our daily automated market-scanning pipeline, which pulls newly listed liquidity pools across DEXs and runs a check-up on each, aggregated into one baseline dataset (roughly 89+ targets, continuously updated).

6. Data freshness

• On-chain state: read live, reflecting the value at the moment the report is generated.
• Market / liquidity: may lag by a few minutes; sourced from public market APIs.
• Market scan library: updated once per day.

7. Data reliability statement

We make every effort to keep data accurate, but public APIs can lag, rate-limit or be briefly unavailable, so individual figures may deviate from the latest state. Report conclusions are risk reference only — see our risk disclosure.