Methodology
How CryptoRadar24 produces each published report — from raw data capture to final verification — and why every figure you see can be traced back to a named public source.
Data sources
We maintain continuous collectors against seven independent public APIs. Every figure in every published report originates from one of these sources, with a timestamp recording when our infrastructure captured it.
Prices, market cap, 24h volume, circulating and total supply across 10k+ assets.
www.coingecko.comTotal Value Locked (TVL) per DeFi protocol and per chain — the single largest capital-flow indicator for DeFi.
defillama.comOpen interest, perpetual funding rates, long/short account ratios — positioning signals that leading spot prices.
www.binance.com/en/futuresCommit counts, unique contributor counts and repo activity per tracked project — a proxy for real developer engagement.
github.comAggregated sentiment score (0–100) combining volatility, momentum, social media, surveys, Bitcoin dominance and trends.
alternative.me/crypto/fear-and-greed-index/Federal Reserve macro data: effective funds rate, M2 money supply, CPI, unemployment — the macro backdrop for every risk asset.
fred.stlouisfed.orgCrypto news headlines and sentiment from major publishers — used only to mark events, never as a source of figures.
cryptopanic.comAnalytical workflow
Each report follows the same multi-step editorial process. Nothing is published until every step has completed and passed internal review.
- 1Query selection
Every report starts from a cross-source analytical query — a SQL question that joins at least two independent data sources. We maintain roughly 100 such queries covering divergences, correlations and anomalies. Source coverage is rebalanced so no single dataset dominates recent output.
- 2Narrative planning
The most significant finding from the query result becomes the centre of the report. A structured outline is drafted: hook, the specific datapoint, historical context, what it may indicate, caveats, and how it relates to other signals the same dataset exposes.
- 3Analysis
The report body is written against the outline, grounded entirely in the numbers returned by the query. Claims outside the data we hold are either omitted or explicitly marked as analytical interpretation rather than fact.
- 4Factcheck
Every numeric claim in the draft is re-queried against the raw dataset to confirm the figure, the units and the time window. Figures that cannot be reproduced from raw data are either corrected or removed.
- 5Correction pass
Any discrepancies surfaced in the factcheck step are corrected in a second editing pass. Chart placeholders are replaced with concrete Chart.js visualizations derived directly from the same query results.
- 6Regional adaptation
Each verified report is adapted — not merely translated — into nine European languages. Regional adaptations preserve every figure exactly and adjust only phrasing, examples and idioms that do not translate cleanly.
Verification
Every numeric claim is re-queried against the raw dataset before publication. Figures that cannot be reproduced exactly against a named public source and a specific timestamp do not appear in the final report.
The factcheck step is mandatory — no report bypasses it, regardless of topic. Reports that fail verification are corrected and re-verified before they are queued for publication.
Regional adaptation
CryptoRadar24 publishes in nine languages: English, German, French, Spanish, Italian, Portuguese, Dutch, Polish and Turkish. Each regional version is an adaptation — it preserves every figure exactly and adjusts only phrasing, examples and idioms that do not translate cleanly.
Regional versions are linked together via hreflang metadata so search engines can serve the correct version for each reader and so translations do not compete against the primary language.
Data freshness and timestamps
Every published report includes a "data snapshot" timestamp indicating the moment our infrastructure captured the figures used. For fast-moving indicators (funding rates, open interest, prices) the snapshot is typically minutes to hours old. For slower-moving indicators (TVL, GitHub activity, FRED releases) the snapshot may be hours to days old depending on the underlying publication cadence.
Corrections and transparency
If you spot an error in a published report, or would like us to disclose the exact data source and timestamp behind a specific figure, please email [email protected]. Verified corrections are applied to the report body and the article is republished with a new "last modified" timestamp.