Understand company-attested participation
Participation attestations are an independent Tracker evidence source when the feature is enabled. Active attestations can connect a builder to the attesting company’s ecosystem even when the builder keeps the proof private on their profile. Managers see the campaign, outcome, and trust state; open disputes remain visible for follow-up but do not contribute to factual summaries or proof-backed filters. Tracker labels organizer evidence as company attested. This means the named company made the assertion; it does not mean Dapping independently verified attendance or an outcome. Participation evidence does not change ecosystem-score weighting in the first release.Choose the right segment
- Projects: inspect deployments, visible activity windows, growth, fees, coverage, and public product context.
- Builders: find people whose profiles show relevant ecosystems, skills, experience, projects, and intentions.
- Companies: understand which company hubs, teams, and public work appear in the selected context.
- Opportunities: review current jobs, grants, bounties, hackathons, accelerators, and events.
Run a practical review
- Select the company and open Ecosystem Tracker.
- Choose the visible period and segment that matches your DevRel, BD, hiring, or program goal.
- Apply filters and note any partial, lower-bound, stale, or unavailable coverage.
- Open the underlying profile, company, project, or opportunity before acting.
- Revisit the same view after a campaign or program to compare like-for-like periods.
Continue on Dapping
Explore company hubs
Complete this task in the Dapping application.
Related guides
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.
Personal profiles and company hubs are different
Understand when to use your own profile and when to use a company hub.

