d.id

Start by claiming a portable identity you control. In d.id, you connect a wallet, generate a DID, and choose what to share. Link a handle, add proofs from email, GitHub, or social profiles, and mint a signed profile credential. Sensitive fields stay private until you allow selective disclosure. Set up recovery with an additional wallet or trusted contacts, and enable key rotation so you can keep the same identity even if a key changes. Scan a QR to sign on mobile, and carry the same profile across apps without creating new accounts.

For organizers, d.id turns membership and roles into verifiable rules. Create a credential schema for Member, Contributor, or Alumni, issue badges individually or via CSV, and define access based on checks rather than screenshots. Use the dashboard to connect Discord, Telegram, or Discourse, map roles to credential predicates, and apply expirations to keep rosters fresh. Build onboarding flows where newcomers complete tasks, submit a simple form, receive a credential, and automatically gain permissions. For events, issue tickets as credentials, verify at entry with a scanner, and prevent transfers or duplicates without exposing personal data.

Builders can drop in identity flows with the SDK. Add Sign-in with DID to replace passwords, verify credentials on the server with a single endpoint, and cache proofs with replay protection. Webhooks let you react to changes—when a user earns a badge, you can unlock features, grant an API key, or trigger payouts. Use sandbox issuers to test edge cases and rate limits to contain abuse. Enforce selective disclosure and consent prompts in production. Pull in anti-sybil signals and reputation scores to filter bots before they touch critical actions. The system speaks common standards (DID, VC), so you can interoperate with existing wallets and proof providers without custom plumbing.

Creators and brands can run trust-based growth without spamming users. Spin up quests that require specific proofs—past purchases, event attendance, or course completion—and reward with roles, discounts, or gated content. Launch allowlists that check for a credential instead of collecting spreadsheets. Collaborate with partners by accepting each other’s credentials, no raw data sharing required. Send targeted updates using a preference center tied to credentials, not emails, so users stay in control. Audience insights aggregate by credential type, helping you see what works while respecting privacy. When a campaign ends, revoke or expire credentials to close access cleanly and keep your community current.