Raw market fields are inputs. The analytical product is YearBull’s. YearBull transforms stored observations into proprietary rankings, market-state indicators, risk classifications, coverage diagnostics, and original research that the upstream dataset does not provide.
What YearBull creates
YearBull Rank, Bull Score, YB Market Risk, Cycle, the Market Bull Index, market participation, coverage diagnostics, exchange concentration summaries, and editorial conclusions are calculated or produced by YearBull. This analytical layer separates the quality and breadth of a move from price movement alone and is not supplied by any external data provider.
Current quantitative inputs
CoinGecko provides the current external market fields used by YearBull: price, market capitalization, reported trading volume, circulating/total/maximum supply where available, exchange reported volume, observed tickers and pairs, venue metadata, and Trust Rank. Trust Rank is an external field and is not proof of reserves, solvency, licensing, custody quality, or withdrawal availability.
The source supplies the listed market and venue fields—not YearBull Rank, Bull Score, YB Market Risk, Cycle, the Market Bull Index, or YearBull’s conclusions. Those outputs are produced from stored observations under the YearBull Methodology Paper. Project websites, technical documentation, repositories, networks, explorers, and exchange websites may also be used as primary sources for identity and editorial research.
Provenance path
- Acquire: permitted fields are collected by scheduled background processes, never by a visitor opening a page.
- Store: dated observations are written to local YearBull tables and caches with their observation or check time.
- Validate: identity, zero/invalid values, stale or frozen observations, missing fields, and internally inconsistent states are checked before analysis.
- Calculate: YearBull metrics are calculated from the completed local dataset in a fixed order.
- Publish: profiles, tables, charts, downloads, and APIs read the same completed state.
- Correct: confirmed identity, source, calculation, or presentation defects follow the public corrections process and material method changes enter the changelog.
Field ownership and freshness
| Public field | Ownership | Freshness reference | Important boundary |
|---|---|---|---|
| Price, market cap, reported volume, supply | External input stored by YearBull | Daily analytics date shown on the profile | Reference observations, not executable quotes |
| Exchange volume, pairs, tickers, Trust Rank | External venue input stored by YearBull | Markets last checked / venue snapshot date | Reported activity is not proof of liquidity or solvency |
| YearBull Rank, Bull Score, YB Market Risk, Cycle | Calculated by YearBull | Completed daily asset snapshot | Comparative research metrics, not price forecasts |
| Market Bull Index and components | Calculated by YearBull | Completed market observation date | Market-state summary; coverage must be read with the value |
| Editorial analysis | YearBull Research | Published / reviewed date | May discuss a dated metric that differs from the current live card |
Freshness and revision policy
The date printed beside a metric is its reference point. This dated-snapshot design keeps rankings, profiles, charts, and downloads internally consistent instead of mixing observations collected at different moments. Values may be delayed, unavailable, revised, or removed when identity or field quality is insufficient; YearBull preserves explicit unavailable and not-ranked states rather than inventing precision.
Analytical snapshots and venue snapshots have separate clocks because they answer different questions. Public pages read the controlled YearBull database and cache, so every visitor sees the same completed analytical state.
Downloads and controls
Download the data dictionary (CSV)
For model disclosure, see the Methodology Paper. For empirical testing and known errors, see Validation, Limitations & Failure Cases. Material changes are recorded in the Methodology Changelog; suspected errors can be submitted under the Corrections Policy.