Start with the product context
- Confirm the product name, description, category, stage, ecosystems, and current official links.
- Inspect the credited team and connected company, then open their full profiles when the relationship matters.
- Read reviews for firsthand context, specificity, disclosed relationships, and recent owner responses.
- Use the product’s own documentation and official website to verify material claims.
- Treat missing information as unknown rather than negative.
Read the deployment first
- Network and contract: confirm the exact chain and address. Similar addresses or tickers on another network are different assets or deployments.
- Contract verification: indicates that source or metadata was verified by the linked explorer or source. It is not a security audit.
- Token information: may include an official token address and market metadata for the selected network. A ticker or price does not prove company ownership.
Interpret activity and coverage
Choose the visible 7-, 30-, or 90-day window when available. Interactions, unique callers, fees, last activity, and growth describe observed on-chain evidence at the displayed coverage.- Complete means the displayed period was covered by the current source and method.
- Lower bound means at least the displayed activity was observed, but more may exist.
- Partial means only part of the expected period or activity was available.
- Stale or unavailable means the data should not be treated as current.
Continue on dApp.ing
Inspect dApps
Complete this task in the dApp.ing application.
Related guides
Use event calendars, side events, Going, and subscriptions
Plan an event week, signal attendance, and follow the calendar without losing the official
registration path.
Search, filter, and browse ecosystem hubs
Search by name or handle, or browse directories with focused filters.
Use dApp Radar to scout and evaluate projects
Use visible project segments and evidence to build a focused scouting list for partnerships,
DevRel, or BD.