Skip to main content
Read the signals on a product page together. No badge, review, contract, or figure establishes safety or quality on its own, and the on-chain numbers in particular claim less than they appear to.
A product should be read across product context, exact-network deployment and proxy status, and timestamped source coverage; metadata is not an audit.

​
Start with the product context

  • Confirm the name, description, category, stage, ecosystems, and current official links.
  • Inspect the credited team and connected company, then open their profiles when the relationship matters.
  • Read reviews for firsthand context, specificity, disclosed relationships, and any response from the product team.
  • Check material claims against the product’s own documentation and website.
  • Treat missing information as unknown rather than negative.

​
Read the deployment

The deployment summary lists production networks, test networks, how many resources have been confirmed out of the total, and the latest activity date. Each deployment then opens into its own detail.
  • Network and address. Confirm the exact chain and the exact address. A similar address or ticker on another network is a different asset.
  • Network confirmation required means Dapping has not yet confirmed which network this address belongs to. Verify it yourself before acting on it.
  • Upgradeable proxy means the contract’s logic can be replaced by whoever controls the upgrade. What you read today is not necessarily what runs tomorrow.
  • Temporarily unavailable means the source could not be reached for this deployment.

​
Interpret activity and coverage

Activity figures are labelled with the window they cover, for example a 30-day interaction count. The window is set by the data source, not chosen by you.
  • A plus sign on a count means activity exceeded the source’s bounded history, so the number is an observed minimum rather than a total.
  • Unavailable in a metric means that figure could not be computed for this deployment, not that it is zero.
  • Every deployment shows As of, its Source, and its Coverage date range, so you can see how far back the record goes.
  • Stale snapshot means the record has not refreshed recently and should not be treated as current.
Token information may include an official token address and market metadata such as market cap, rank, circulating supply, and total supply for the selected network. A ticker or a price does not prove that a company owns the token. Use the explorer and source links to check anything you are about to act on. On-chain metadata is not proof of ownership, protocol revenue, user count, legal status, or safety. It is not an audit, and it is not investment advice. Dapping cannot reverse a blockchain transaction you sign.

​
Continue on Dapping

Inspect products

Open a product page to read its deployments, official links, and observed on-chain activity together.

Use event calendars, 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.
Last modified on August 26, 2026