Every claim needs a source.
Evidence, availability and organizational roles answer different questions. We keep those answers separate.
What a label means
| Evidence | Meaning |
|---|---|
| Project confirms live | The project’s own announcement or documentation explicitly confirms production Arc support. |
| Issuer says live | Circle or an issuer reports launch availability; specific markets still need checking. |
| Platform documented | A specific component is described in official technical documentation. |
| Launch named / Directory only | An organization appears in launch materials or the official directory. This does not establish deployment. |
| Testnet demonstrated / Prototype only | Evidence describes a testnet demonstration or an experimental submission. |
| Validator announced | Cohort membership is announced; activation and voting weight require separate evidence. |
| Grant confirmed | A grant relationship is established. It does not prove mainnet use. |
Publishing and corrections
Primary sources support factual changes. Automated collectors may publish changes that satisfy their source-specific checks; contradictions and ambiguous changes enter a review queue. Model agreement is not evidence. Editors can lock corrected fields and revert revisions.
Data freshness
Network data is collected every five minutes, employer jobs hourly and research sources daily while the worker runs. Failed requests never become zero values. Older measurements keep their timestamps and become stale after fifteen minutes.
Counts and financial figures
Our record count includes organizations, products, assets and prototypes. It is not a count of live applications. Funding figures, supply statements and token prices are dated and attributed; presale prices are not live quotes.
Community reviews
Reviews reflect users’ experiences. Only approved reviews contribute to public ratings. Updating a review returns it to moderation. A founder’s identity or a user rating is not a security audit.
Suggest a correction ↗