Methodology

How to interpret proof and platform signals

Dapping combines user-provided information, accountable relationships, visible activity, public sources, and review workflows. These signals help people investigate claims, but they are context, not guarantees.

Last updated 24 July 2026

Where information comes from

Public pages can include information supplied by a person or company, confirmed through another Dapping participant, connected from an external account, obtained from a public source, or maintained by Dapping for discovery.

The source and state matter. A self-described skill is different from verified experience. A connected account is different from ownership of every item visible through that account. A public blockchain record is different from an audit or an identity check.

How to read common forms of evidence
EvidenceWhat it can showWhat it does not prove
Verified experienceA qualifying relationship or source supported the roleQuality of work, current employment, or future performance
Inspectable workA project, dApp, or public contribution can be reviewedAuthorship of every part or security of the product
Connected accountThe user authenticated or linked the supported accountEvery public claim made on that external service
Recommendation or endorsementAnother participant supplied professional contextIndependent verification or a Dapping endorsement
On-chain recordA public network recorded the displayed activityIdentity, ownership, revenue, safety, or investment quality

The proof hierarchy

Start with the strongest evidence that is relevant to the decision. Verified experience and inspectable work usually deserve the most attention. Company context, connected accounts, recommendations, endorsements, current intentions, activity, and Karma can add useful support.

Do not replace a complete review with a single badge, score, follower count, or match indicator. Signals can be incomplete, outdated, disputed, or based on information that is not visible to Dapping.

Verification is earned, not bought

A person or company cannot purchase a Dapping verification badge. Verification is earned when the required public and private qualifying signals support the identity or relationship being represented and the applicable review is completed.

Verification can be pending, rejected, reset, or removed when information changes, supporting evidence is no longer valid, a relationship ends, or a review identifies a problem. The badge represents the verified scope shown by the product, not general approval by Dapping.

Karma reflects sustained professional credibility

Karma is a proof-led reputation signal built around five pillars: foundation, proof, validation, contribution, and momentum. It helps surface participants who are building a credible record over time. It is not a financial score, employment rating, identity guarantee, or measure of personal worth.

The strongest way to improve Karma is to improve the underlying professional record. Complete an accurate profile, add inspectable projects, verify eligible experience, keep availability current, connect relevant professional accounts, contribute useful reviews or comments, and earn specific recommendations or endorsements from people with firsthand context.

  • Prioritize accurate, current proof over adding a large volume of weak claims.
  • Ask for recommendations that describe the work, relationship, and outcome instead of generic praise.
  • Endorse skills only when you have a genuine basis for doing so.
  • Update completed roles, shipped projects, grants, hackathons, and availability.
  • Participate consistently and constructively instead of creating reciprocal or artificial activity.

Matching and discovery

Search, recommendations, and match indicators can use available profile, listing, relationship, category, ecosystem, location, skill, intent, freshness, and activity context. The exact context available varies by surface and can be incomplete.

A match indicator explains potential relevance. It does not determine eligibility, ranking in an employer's process, selection for an opportunity, or the quality of either party. Publishers and applicants remain responsible for checking requirements and fit.

On-chain data and coverage

On-chain information is tied to the exact network and identifier displayed. Coverage labels explain whether a result is complete for the stated window, a lower bound, partial, stale, unavailable, or still being qualified.

Activity counts can depend on the supported network, provider coverage, time window, parsing rules, and data availability. They are not revenue measurements, ownership proof, security audits, or investment recommendations.

Corrections and changing information

Profiles, company hubs, listings, relationships, and external data change. Owners can update eligible information, and users can report inaccurate, duplicate, impersonating, or harmful content through the relevant product surface or support.

Dapping may correct, relabel, restrict, or remove content after review. Public explanations describe outcomes and available user actions without exposing private evidence, abuse signals, or review procedures.