> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dapp.ing/llms.txt
> Use this file to discover all available pages before exploring further.

# Build proof without revealing your identity

> How a pseudonymous builder accumulates verifiable proof on Dapping, and which signals need a name attached.

Plenty of serious Web3 work is done under a handle. Dapping never asks for a legal name, and most of the proof on a profile is available to you whether or not anyone knows yours.

## What the account itself needs

You can create an account with a wallet alone. The name you set during onboarding is a display name, not a legal one, and your handle is the durable address people share. Nothing checks either against a document.

You will still need an account email eventually: it carries notifications and security alerts, and a verified one is required before any create form will save. It is never shown on your profile, and it does not have to carry your name.

## Proof you can build under a handle

* **Products you shipped.** Publish them, or accept team credit on someone else's, and the credit sits on your profile under the name you use.
* **Recommendations and skill endorsements.** Written by people who worked with you, about work rather than identity.
* **Participation attestations.** An organizer confirms the account took part in their campaign. They are attesting participation, not vouching for who is behind the handle.
* **Published writing.** Your Dev.to articles, confirmed through an account you already connected.
* **Community board standing.** Ranked on contribution, with the rules published on the board.

That is most of the graph, and none of it requires you to be identifiable.

## Where a name gets involved

**Verified experience is the exception, and only towards one party.** Both routes to it involve a company knowing who you are: an attestation is approved by someone at that company who can confirm you held the role, and a work-email check needs an address on their domain. Neither publishes your name or your email. What appears is the label on that one role.

**The verified profile badge has a fixed checklist**, and part of it is connected accounts: a verified email, a connected X account, and a connected Discord or GitHub account. Those can be pseudonymous accounts, but they do have to exist and be yours.

## Decide what is public

Location, Company and Position, Primary Wallet, Social Accounts, Open to Work, and NFT Collection each have their own switch under **Privacy**. Only your primary wallet is ever shown, never the full list, and collectibles appear only while Primary Wallet is on, because showing what a wallet holds reveals the wallet.

Think about the wallet one carefully. An address on a public profile links your Dapping identity to everything that address has ever done, which is the single fastest way to undo a pseudonym.

## Continue on Dapping

<Card title="Review what your profile shows" href="https://dapp.ing/userprofile?account=privacy">
  Open privacy settings to check which optional fields are public before you share your profile.
</Card>

## Related guides

<CardGroup cols={2}>
  <Card title="Create an account and choose a sign-in method" icon="book-open" href="/help/getting-started/create-an-account-and-choose-a-sign-in-method">
    Use an approved login method, then connect professional accounts without confusing them with
    recovery methods.
  </Card>

  <Card title="Add and verify professional experience" icon="book-open" href="/help/profiles/add-and-verify-professional-experience">
    Add a role and request confirmation through a company attestation or a work email.
  </Card>

  <Card title="Manage profile visibility, notifications, and digests" icon="book-open" href="/help/account-safety/manage-profile-visibility-notifications-and-digests">
    Choose which profile details are public and which notifications you receive.
  </Card>
</CardGroup>