Unknown ≠ 0
If a source or field is missing, the information remains unknown. It must not artificially push a score down or up.
Transparency · data quality
What we know, where it comes from — and where the gaps are.
Dudelytics does more than show sources. This page also explains how often data is updated, what history actually exists, what happens during outages, and what a source does not allow us to claim.
Short version: unknown is not zero, an older but valid trading day is not automatically stale, a proxy remains a proxy — and a pretty number does not get a PhD from us.
Dudelytics rules
Four rules before every number
Source ≠ interpretation
Providers supply facts or raw data. Dudelytics visibly separates them from its own derivations, proxies, scores and Dude takes.
Outage ≠ data deletion
If a provider fails temporarily, the last valid snapshot remains. The state is degraded or marked older — not set to zero.
Freshness needs context
Five-minute crypto data, daily FRED series and US ETF trading days run on different clocks. Dudelytics therefore evaluates freshness relative to the source.
Live · server-side
Freshness of central data families
For these core datasets, the Web App does not wait on external providers. An authenticated scheduler collects provider data centrally; views then read only the latest local snapshot. This keeps the interface fast and prevents one slow provider from blocking the page.
Central Data Hub 0.24g-sdv2:
The timestamp below describes the Dudelytics snapshot. For sources with their own publication cadence — especially FRED and US ETF flows — the substantively relevant source date can be older and still be correct.
| Data family | Regular cadence | Latest Dudelytics snapshot | Freshness |
|---|---|---|---|
| Watchlist market | 5 min | Oct 2, 2026, 9:01 AM7 min ago | Refresh overdue |
| Spot market | 5 min | Oct 2, 2026, 9:01 AM7 min ago | Refresh overdue |
| Multi-exchange derivatives | 5 min | Oct 2, 2026, 9:01 AM7 min ago | Refresh overdue |
| Derivatives context | 5 min | Oct 2, 2026, 9:01 AM7 min ago | Refresh overdue |
| Overall-market trends | 5 min | Oct 2, 2026, 9:01 AM7 min ago | Refresh overdue |
| Crypto macro | 5 min | Oct 2, 2026, 9:01 AM7 min ago | Refresh overdue |
| Speculative Heat | 30 min | Oct 2, 2026, 8:55 AM13 min ago | Fresh |
| Research pulse | 15 min | Oct 2, 2026, 9:01 AM7 min ago | Fresh |
| News Radar | 15 min | Oct 2, 2026, 9:01 AM7 min ago | Fresh |
| ETF flows | 30 min | Oct 2, 2026, 8:31 AM36 min ago | Last valid value as scheduled |
| ETH staking | 30 min | Oct 2, 2026, 9:05 AM3 min ago | Fresh |
| ETH value capture | 30 min | Oct 2, 2026, 8:45 AM22 min ago | Fresh |
| Macro & US liquidity | 1 h | Oct 2, 2026, 8:50 AM17 min ago | Fresh |
| Macro trend series | 1 h | Oct 2, 2026, 8:50 AM17 min ago | Fresh |
| ETH exchange supply | 4 h | Oct 2, 2026, 8:25 AM42 min ago | Fresh |
| Bitcoin network | 15 min | Oct 2, 2026, 8:50 AM17 min ago | Scheduler run due |
| Security Radar | 1 h | Oct 2, 2026, 9:01 AM7 min ago | Fresh |
| Whale Radar · Ethereum | 5 min | Oct 2, 2026, 9:01 AM7 min ago | Refresh overdue |
| Whale Radar · Bitcoin Mempool | 5 min | Oct 2, 2026, 9:01 AM7 min ago | Refresh overdue |
| Whale Radar · Bitcoin Block | 5 min | Oct 2, 2026, 9:01 AM7 min ago | Refresh overdue |
| BTC holder picture · 155D mobility | 6 h | Oct 2, 2026, 8:45 AM22 min ago | Fresh |
| BTC exchange proxy | 6 h | Oct 2, 2026, 5:20 AM3 h ago | Fresh |
Source catalog
Source, coverage, history, fallback and limits
“Coverage” here means which Dudelytics feature this source meaningfully feeds. It explicitly does not mean Dudelytics fully covers every coin, every exchange or every conceivable crypto-market metric.
Market & indices
DPMI Index Family & central market data
Central Data Hub- Source
- CoinGecko
- Coverage
- Main DPMI, DPMI Holder Quality, seven DPMI sector indices, productive-market pool, and the central price/market-cap/volume base for Watchlist and coin context. Dudelytics also publishes the daily DPMI/BTC/overall-market benchmark and Dude-VIX/DVIX from stored DPMI/sector observations.
- Update cadence
- Core market data and DPMI normally update about every 5 minutes; coin metadata is cached separately. The benchmark uses a daily 00:00 UTC target. CoinGecko /global is captured around that target during the regular five-minute scheduler runs and may retry until 00:20 UTC. The completed BTC daily point is added from 00:10 UTC. There is no additional 00:40/01:00 finalization stage.
- Data freshness
- Watchlist market: Refresh overdue (7 min ago)
- History
- DPMI: real observed history plus clearly separated backfill. Sector indices mature exclusively from real observations; no artificial sector backfill. The benchmark normalizes the first complete daily point to 100 and keeps target, source and retrieval times separate.
- Fallback / degradation
- The last valid central snapshot remains visible. Missing or failed provider responses are not interpreted as zero.
- Limits
- CoinGecko supplies raw market and metadata. Categories or descriptions are not automatic evidence of productivity, fundamentals or token value capture. In the benchmark, CoinGecko Total Market Cap deliberately includes stablecoins. DPMI uses the last real observed point at or shortly before 00:00 UTC; BTC uses the completed CoinGecko daily point for 00:00 UTC; the overall market is captured from CoinGecko /global around the target. The provider-owned updated_at timestamp must lie within ±10 minutes and the retrieval routine remains open until 00:20 UTC. Target, source and retrieval times remain separate. Missing values are neither interpolated nor filled with previous-day values.
Overall market, dominance & crypto sentiment
Central Data Hub- Source
- CoinMarketCap · Keyless Public API CoinGecko Global · supplementary
- Coverage
- Total market capitalization, 24h volume, BTC/ETH dominance, CMC20, Fear & Greed, Altcoin Season, and overall-market trends.
- Update cadence
- Crypto macro about every 10 minutes; central trend snapshots about every 5 minutes. Individual provider histories have their own cadence.
- Data freshness
- Crypto macro: Refresh overdue (7 min ago) · Overall-market trends: Refresh overdue (7 min ago)
- History
- Dudelytics stores its own observed market trends; available CMC histories are added for CMC20, Fear & Greed and Altcoin Season.
- Fallback / degradation
- Individual metrics may fail without setting the entire block to zero. An existing stale snapshot can explicitly remain visible.
- Limits
- Fear & Greed, CMC20 and Altcoin Season are provider metrics. The 24h turnover ratio is a market-activity/liquidity proxy, not global monetary liquidity.
Speculative Heat / performance rotation
Central Data Hub- Source
- CoinGecko CoinGecko Onchain · via Dudelytics Onchain Market Service Dudelytics DPMI
- Coverage
- Broad meme/hype momentum, the lower half of the Top-25 meme cohort by market cap as a speculative small-cap proxy, 24h turnover ratio, newly observed DEX pools, and relative strength versus the productive DPMI.
- Update cadence
- Collected centrally about every 30 minutes. DEX-pool changes are counted only between these real observations.
- Data freshness
- Speculative Heat: Fresh (13 min ago)
- History
- Dudelytics stores up to 14 days of its own observed sensor points. The first DEX observation only establishes the baseline; there is no artificial backward backfill for new pools.
- Fallback / degradation
- The last valid Central Data Hub snapshot remains readable. CoinGecko category market data may temporarily come from an existing cache during provider errors or budget limits; missing components are removed from score weighting rather than set to zero.
- Limits
- The sensor measures speculative activity and relative performance, not directly observed capital flows. CoinGecko categories are provider classifications. New DEX pools indicate activity, not automatically adoption, quality or security. The DPMI itself is not changed by this sensor in either eligibility or weighting.
Spot-market proxy
Central Data Hub- Source
- Binance Spot
- Coverage
- Selected liquid USDT spot pairs, a broad spot-volume proxy, and BTC/ETH/SOL spot-versus-futures context.
- Update cadence
- Collected centrally about every 5 minutes.
- Data freshness
- Spot market: Refresh overdue (7 min ago)
- History
- Primarily snapshot/provider context; where Dudelytics shows trends, they come from observations actually stored.
- Fallback / degradation
- If a provider fails, the last local snapshot remains available as long as it can be identified as such.
- Limits
- Explicitly a Binance proxy — not a complete global spot market and not proof of activity across all exchanges.
Multi-exchange derivatives
Central Data Hub- Source
- Binance Futures OKX Bybit
- Coverage
- Cross-exchange comparison layer for BTC and ETH: open interest, funding, long/short accounts and taker flow, depending on exchange and available metric.
- Update cadence
- About every 5 minutes.
- Data freshness
- Multi-exchange derivatives: Refresh overdue (7 min ago) · Derivatives context: Refresh overdue (7 min ago) · derivatives_summary: no public state
- History
- Compact local observed history of BTC/ETH aggregates. Incompatible provider histories are not artificially reconstructed.
- Fallback / degradation
- Individual exchanges may fail; coverage is reduced per metric. An aggregate can continue as long as at least one exchange supplies usable data. If the entire refresh fails, the previous snapshot is retained.
- Limits
- Three major exchanges are not a complete global derivatives market. Dudelytics does not, for example, invent OKX 24h OI history from incompatible units.
US spot ETF flows
Central Data Hub- Source
- Farside Investors · Bitcoin Farside Investors · Ethereum
- Coverage
- Currently BTC and ETH: net flows from the supported US spot ETF tables.
- Update cadence
- About every 30 minutes during relevant US trading/publication windows; deliberately quieter overnight, on weekends and on holidays.
- Data freshness
- ETF flows: Last valid value as scheduled (36 min ago)
- History
- Persistent structured history in the Market Data DB; fully reported provider observations are stored by trading day and can be updated date-for-date when Farside later revises data.
- Fallback / degradation
- Freshness beats row count: Dudelytics first requests a timestamped Farside target path through the live-reader relay; direct Farside responses remain authoritative when STRATO can reach them. Clean/cached reader URLs, the Market Data DB and a dated verified bridge snapshot serve continuity only.
- Limits
- No zero value for unpublished, weekend or holiday data. Partially reported new days are visibly marked preliminary, but enter the score, 5/20-trading-day context and observed history only after complete reporting. A lag of more than one expected US trading day becomes visible as a degradation in the Dude Report.
Macro & liquidity
US macro & liquidity context
Central Data Hub- Source
- FRED · Federal Reserve Bank of St. Louis
- Coverage
- US 2Y/10Y Treasury yields, broad US Dollar Index, VIX, Fed balance sheet, Treasury General Account, and Overnight Reverse Repo.
- Update cadence
- Dudelytics checks roughly hourly. The underlying FRED series themselves publish daily or weekly depending on the series.
- Data freshness
- Macro & US liquidity: Fresh (17 min ago) · Macro trend series: Fresh (17 min ago)
- History
- FRED time series with individual source data dates; Dudelytics derives 5D/7D/28D context and a simplified liquidity proxy.
- Fallback / degradation
- The last valid cache can continue to be used during a temporary FRED outage; individual source dates are not artificially aligned to the same day.
- Limits
- The simplified liquidity proxy is Fed balance sheet − TGA − ON RRP. It is US-centric, not a global liquidity measure and not an isolated trading signal.
Research & fundamentals
News & research context
Central Data Hub- Source
- CoinDesk Cointelegraph Decrypt The Block
- Coverage
- Market News Radar and Research Pulse; items are deduplicated, classified by topic and treated as context.
- Update cadence
- About every 15 minutes.
- Data freshness
- News Radar: Fresh (7 min ago) · Research pulse: Fresh (7 min ago)
- History
- No claimed full media archive. Dudelytics works with currently available feed content and its own frozen briefing/research artifacts.
- Fallback / degradation
- The last valid feed snapshot can remain visible for a limited time. If an item or reliable date is missing, it is not invented retroactively.
- Limits
- News does not change a market score. An AI language/translation layer may prepare text, but it is not the factual source of the item.
Security Radar
Central Data Hub- Source
- SlowMist Hacked
- Coverage
- Broad incident discovery for protocols, chains, bridges, exchanges, wallets and other crypto infrastructure. Ongoing cases can be curated and updated through official primary sources.
- Update cadence
- Regular discovery about every 6 hours. Known serious cases can be rechecked about every 2 hours; critical cases hourly.
- Data freshness
- Security Radar: Fresh (7 min ago)
- History
- Dudelytics builds its own deduplicated incident history. Updates remain attached to the same incident; historical backfills are assigned to the actual incident date and do not trigger a new user alert.
- Fallback / degradation
- Provider errors do not overwrite the last valid incident state. The Web App reads only the local Central Data Hub snapshot, or the local curated seed before the first scheduler run.
- Limits
- Dudelytics is not a real-time alert service. Discovery items are not automatically official confirmation. Threat level and confirmation status are tracked separately; primary sources take precedence in ongoing updates.
Coin Quality & Hot or Not
coin/view-dependent- Source
- CoinGecko DefiLlama GitHub Coin Metrics Community Snapshot
- Coverage
- Per coin, including maturity, market structure, tokenomics, developer activity, usage/adoption, revenue/fees, value capture, security and governance — only to the extent robust data is available.
- Update cadence
- Coin-dependent/on demand; the Quality data path normally caches a coin for 6 hours.
- Data freshness
- Coin/request-dependent; there is no single global freshness state for this data family.
- History
- No artificial fundamentals backfill. Then→Now comparisons freeze Dudelytics observation snapshots; provider histories are used only when they actually exist.
- Fallback / degradation
- An existing per-coin cache can serve for up to 48 hours as an explicitly older fallback. Individual sources may be missing without contributing zero to the Quality Score.
- Limits
- Coverage depends on the asset. Missing data lowers data coverage; it is not a negative fundamental judgment. Official primary-source profiles supplement standard APIs where robust evidence would otherwise be missing.
Ethereum & onchain
Ethereum staking
Central Data Hub- Source
- ValidatorQueue.com validatorqueue-com · Open Source
- Coverage
- Staked ETH, staking share, active validators, APR, plus entry/exit queues and waiting times.
- Update cadence
- About every 30 minutes in the central Data Hub.
- Data freshness
- ETH staking: Fresh (3 min ago)
- History
- Open historical daily data from the ValidatorQueue project is imported into the Market Data DB for a limited recent window.
- Fallback / degradation
- The live page and open GitHub repository serve as transport fallbacks for each other; the last valid Dudelytics snapshot remains available.
- Limits
- ValidatorQueue names beaconcha.in as the queue source. The entry queue is not proof of buying; the exit queue is not proof of selling. The sensor describes staking structure, not spot order flow.
Ethereum fees, burn & value capture
Central Data Hub- Source
- DefiLlama ultrasound.money · supplementary
- Coverage
- Ethereum dailyFees, dailyRevenue/burn context, ETH price reference, plus a supplementary PoS issuance reference.
- Update cadence
- About every 30 minutes.
- Data freshness
- ETH value capture: Fresh (22 min ago)
- History
- Provider ranges are used for current versus 7D/30D context; observed sensor states can additionally be stored in structured form.
- Fallback / degradation
- Partial sources may be missing. The sensor can continue with reduced coverage; a previous valid snapshot is retained as a degradation state.
- Limits
- Fees/burn show network usage and monetary mechanics, but not an isolated buy/sell signal. Net new issuance is calculated only when price and issuance references are robust.
Ethereum exchange-supply proxy
Central Data Hub- Source
- Binance Proof of Reserves Bybit Proof of Reserves DefiLlama CEX adapters PublicNode · Ethereum RPC
- Coverage
- Transparent cohort of known CEX/PoR wallets for native ETH, including Binance, Bybit and open DefiLlama CEX adapters.
- Update cadence
- A new observation normally about every 4 hours; short-term retry attempts are limited.
- Data freshness
- ETH exchange supply: Fresh (42 min ago)
- History
- Own observed history of the transparent wallet cohort.
- Fallback / degradation
- The wallet registry and last valid snapshot remain local; individual exchange/wallet sources can reduce coverage.
- Limits
- Proxy for a transparently observable wallet cohort — not a complete global exchange balance and certainly not ETH freely offered in order books.
Ethereum Whale Radar
Central Data Hub- Source
- PublicNode · Ethereum Cloudflare Ethereum Gateway · fallback
- Coverage
- Native ETH transfers from recent Ethereum blocks with statistical thresholds and local pattern context.
- Update cadence
- About every 5 minutes.
- Data freshness
- Whale Radar · Ethereum: Refresh overdue (7 min ago)
- History
- Short local observation memory for recurring large transfers/patterns.
- Fallback / degradation
- Several public RPC providers are tried in sequence; one provider failure does not immediately stop the sensor.
- Limits
- A transfer is not a buy or sell. Without robust entity/DEX evidence, accumulation/distribution statements remain conservative transfer patterns.
Bitcoin & onchain
Bitcoin network · hashrate & difficulty
Central Data Hub- Source
- mempool.space · REST API
- Coverage
- Estimated network hashrate, smoothed 7D/30D hashrate trends, current difficulty, last adjustment, ongoing estimate of the next difficulty adjustment, retarget progress, remaining blocks and expected retarget time.
- Update cadence
- Difficulty/retarget context about every 15 minutes in the Central Data Hub; the one-year hashrate history is deliberately reloaded from the provider only about every 6 hours and reused locally in between.
- Data freshness
- Bitcoin network: Scheduler run due (17 min ago)
- History
- The one-year mempool.space history is used for 30D/90D/1Y comparisons. Hashrate and difficulty are indexed to 100 at the start of the selected Market Overview range; there is no misleading dual axis.
- Fallback / degradation
- The last valid Dudelytics provider cache is retained. A temporary mempool.space error never replaces hashrate, difficulty or the estimate with zero.
- Limits
- Hashrate is an estimate derived from observed block production and difficulty, not a directly measured gauge. The projected next difficulty change evolves until the actual retarget and is not a BTC price signal.
Bitcoin Whale Radar
Central Data Hub- Source
- mempool.space PublicNode · Bitcoin RPC
- Coverage
- Current large mempool transactions plus confirmed-block context with inputs, outputs and UTXO patterns.
- Update cadence
- About every 5 minutes.
- Data freshness
- Whale Radar · Bitcoin Mempool: Refresh overdue (7 min ago) · Whale Radar · Bitcoin Block: Refresh overdue (7 min ago)
- History
- Local 24h memory for relevant mempool/address patterns; confirmed blocks are observed without interpreting a lack of movement as zero activity.
- Fallback / degradation
- Mempool and block sensors are separate paths. A quiet or failing part does not erase the other.
- Limits
- Bitcoin change, batch transactions and internal wallet organization make entity statements difficult. A large output is not automatically an external recipient or a purchase.
Bitcoin holder mobility & CEX-wallet proxy
Central Data Hub- Source
- Open Bitcoin Metrics DefiLlama · CEX adapters CoinGecko · price fallback
- Coverage
- Mobility of BTC outputs at least 155 days old plus a transparent CEX-wallet/PoR proxy for Bitcoin holdings.
- Update cadence
- About every 6 hours.
- Data freshness
- BTC holder picture · 155D mobility: Fresh (22 min ago) · BTC exchange proxy: Fresh (3 h ago)
- History
- Open Bitcoin Metrics provides daily history; the CEX proxy builds its own observed comparison points for 1D/7D/30D.
- Fallback / degradation
- The last valid sensor state is retained; for the CEX proxy, BTC/USD can come from DefiLlama with CoinGecko as a price fallback.
- Limits
- 155D mobility is a UTXO/spent-value proxy, not classic entity-adjusted LTH supply. The CEX proxy is not a complete global exchange balance and not proof of selling.
Public data
DPMI also remains machine-readable
The transparency page explains the sources. In addition, the DPMI Index Family publishes current values, history, composition, DPMI Holder Quality, Sector Family, DPMI Fear & Greed, Dude-VIX/DVIX and the daily DPMI/BTC/overall-market benchmark as read-only data.
ETF transport fix 0.32p-r4: STRATO forensics showed that the generic browser HTTP helper receives a different r.jina.ai response without the ETF table, while the precisely diagnosed Jina request returns the current Farside Markdown table. ETF flows therefore use a dedicated Jina request path with exactly one Markdown Accept header, X-Return-Format: markdown, no-cache and the diagnostically confirmed user agent.