What an attestation says
Each attestation ties a builder to one of your campaigns: an event, hackathon, grant, bounty, or accelerator. It records an outcome, participant or winner, and can carry a role such as speaker, organizer, mentor, judge, moderator, or volunteer. Issuing them requires a verified company, because the attestation borrows your identity’s weight. Outcomes only move up. A participant can later be promoted to winner, and a winner is never demoted, including by accident: re-import the same campaign with everyone listed as a participant and your winners stay winners. If one file names the same person twice with different outcomes, the stronger one is what publishes. Corrections happen by revoking, which removes the attestation cleanly and visibly rather than rewriting history.Import a campaign in one pass
From your hub’s Activities page, choose the campaign, download the template, and upload a CSV of up to 500 rows of Dapping handles or profile URLs, optionally with an outcome column and a role column. You always see a preview before anything publishes: new attestations, promotions, rows already attested, duplicates within the file, and handles that do not match an account. Nothing is issued until you publish the batch, and re-uploading the same file is safe. Unmatched participants are worth revisiting after the event, since people often join Dapping once they hear an attestation is waiting.What the recipient controls
An attestation lands in the builder’s inbox, and they choose whether it shows on their profile. They can dispute one they believe is wrong, and while a record is contested it stops counting as proof: it leaves your attestation totals, it stops qualifying under the attested filters, and it is marked disputed wherever it still appears. You can withdraw a disputed attestation; you cannot overrule the person, and Dapping reviews any dispute you stand behind. This consent step is why attestations read as credible: nobody is forcibly labeled, and a disputed record says so.After the batch publishes
Attestations start working immediately. They appear in your Ecosystem Tracker as proof-backed engagement, they credit your community board if you attached campaign XP, and they feed each builder’s Karma as independent validation. Come back to the unmatched rows a week later, once the people who joined to claim theirs have accounts. They also make the next campaign easier to recruit for, because the last one left evidence. An organizer who attests reliably becomes one builders seek out. An attestation records participation, not quality: a winner outcome is your decision, not an independent assessment of the work. How proof works covers what it certifies and where it stops.Continue on Dapping
Open your company hub
Open the Activities page on your hub to import a campaign and issue attestations.
Related guides
Run community boards
Turn attested campaigns into a public leaderboard with published rules.
Use Company Activity to track work and follow up
The activity feed, listing performance, and the attestation panel in detail.
Publish programs and events
Run the campaigns that attestations later make verifiable.