> For the complete documentation index, see [llms.txt](https://docs.tachyo.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tachyo.ai/under-the-hood/data-sources.md). # Where the data comes from Tachyo is a data platform before it is a model. Most of the engineering is in collecting on-chain history properly and keeping it current: the scoring on top is the last mile. ## What is collected **On-chain history** on Solana, Ethereum, BNB Chain, Base, Robinhood and Stables: swaps, transfers, balances, holder censuses per token, and the funding relationships between wallets that reveal clusters. **Market data**: price, market cap, liquidity, volume, and the pool-level detail needed to tell a real move from a thin one. **Contract safety**: mint authority, liquidity locks, honeypot behaviour, taxes and the rest of the standard rug surface. **Social and KOL activity**: who is naming a contract publicly on X, with the reach behind the account, plus the wallet-to-person mapping that lets us compare what someone says with what their wallet does. **Platform-native activity**: theses, positions and behaviour from the FOMO ecosystem, which is where much of the qualitative layer comes from. ## How often it moves * **Continuously**: price, market cap, liquidity, and the live trade feed. * **Hourly**: the signal scan that produces token verdicts. * **Nightly**: the full recompute, with hundreds of thousands of wallets rescored, the follow graph behind [Alpha](/platform/alpha.md) rebuilt, holder censuses refreshed. * **Weekly**: the model behind the top of the tier ladder is retrained. * **On demand**: you can force a token re-scan; see [Snapshots and freshness](/concepts/freshness.md). As of August 2026 the platform has profiled **over 500,000 wallets**, adding roughly **8,000-9,000 new profiles a day**. ## Where coverage ends, honestly * **Six chains are scored end to end**, and the list grows: when a new chain starts carrying real volume we add it. Others may appear through market data and safety checks, without a meaningful tier picture. * **Coverage is not uniform across them.** A token with many unrated holders is usually telling you about our history depth on that chain, not about the token. * **Tracked-wallet volume is not market volume.** Anywhere the product says FOMO volume or tracked volume, it means our population: a token can be busy on the open market and silent in ours. * **Some rows come from frozen sources.** Where a value was captured on a specific date, the row says so rather than presenting it as current. ## The rule underneath all of it **A failed measurement never renders as a zero.** A dash means we could not measure; a zero means we measured nothing. Sources fail, APIs rate-limit, chains reorganise. When that happens the product says "unknown" and keeps the last good value rather than publishing a confident wrong number. The same discipline applies to the pipelines themselves: a nightly recompute that comes back implausibly empty is rejected rather than allowed to overwrite good data with a degenerate result. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.tachyo.ai/under-the-hood/data-sources.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.