Data sources
Every score is grounded in real on-chain data, pulled live at request time from established providers and block explorers, then cached briefly for speed.
On-chain data
CSDS reads directly from each supported chain through established RPC and block-explorer infrastructure. The categories of data we pull:
| Chain | What we read |
|---|---|
| EVM (Ethereum, BNB) | Contract verification & source code, holders, transactions, liquidity reserves, owner/admin functions. |
| Solana | Mint & freeze authority, account data, holder distribution, token metadata. |
What we read on-chain
- Contract: verification status and source (EVM), program data (Solana), proxy/upgrade mechanisms.
- Authority & ownership: mint/freeze authority (Solana), owner/admin functions (EVM), ownership-transfer events.
- Holders: top-holder balances and distribution; known CEX wallets are excluded so exchange custody doesn't read as concentration.
- Liquidity: DEX pool reserves, pairing, and lock status.
- Trading: recent volume and price vs. a multi-week historical baseline.
Off-chain signals
For deeper reports, CSDS can scrape a project's public website and analyze the content with an LLM to surface claims, team signals, and inconsistencies. These signals supplement — never replace — the on-chain evidence.
Freshness & caching
- On-chain reads are live at request time (seconds of delay at most).
- Results are cached for 24 hours; repeat checks of the same token can return cached data.
- Historical baselines are aggregated over multiple weeks to detect spikes.