Skip to main content
Portfolio projects give people something concrete to inspect on your profile. A dApp can be published by a person or company and can credit other contributors without giving them ownership of the listing.

​
Add your own project

  1. Use Publish → dApp and choose the correct posting identity.
  2. Add the product name, summary, description, category, stage, ecosystems, links, and media.
  3. Add only team members who actually contributed and choose the role that matches the access they need.
  4. Submit the listing and review its public product page.

​
Respond to a team-credit request

When another owner or admin adds you, the request appears in your account queue. Approve it to appear as an accepted team member or reject it if the association is wrong. Pending or rejected requests are not public team credit.

​
Team access is not company employment proof

A dApp owner, admin, editor, or viewer role controls that product’s collaboration access. It does not prove employment at the associated company and does not transfer ownership of your personal profile. After shipping, update the project status, working links, networks, and your contribution. A repo, product page, demo, contract, or public milestone gives reviewers something to inspect. Do not add yourself to a dApp team unless you performed the stated work and can accept the team request.

​
Continue on dApp.ing

Browse or publish dApps

Complete this task in the dApp.ing application.

Why experience verification can reset, be rejected, or be revoked

See why changing a role or its evidence can remove an existing verification.

Add skills and endorse another builder

Keep your skill list focused and endorse work you have seen firsthand.
Last modified on July 24, 2026