Web3 identity tools connect wallets, names, decentralized identifiers, credentials, reputation, or access rights. These components solve different problems: an address can authorize an action, but it does not automatically prove a legal identity or preserve privacy.
Identify what the system actually proves
- • Identifier: who creates, controls, updates, and resolves it?
- • Credential: who issues it, what claim does it contain, and can it be revoked?
- • Disclosure: which details become public and can only necessary facts be shared?
Check control, portability, and recovery
A wallet-bound identity may be portable across compatible applications but difficult to recover after key loss. A hosted service can offer easier recovery while adding provider dependence. Review account linking, key rotation, guardians, export, supported networks, contract upgrades, and what happens if the issuer or interface disappears.
Privacy requires more than a pseudonym
Public transactions can connect addresses, names, memberships, and activity over time. Encryption or zero-knowledge proofs may limit disclosure, but implementation and metadata still matter. Do not place sensitive personal data permanently on a public blockchain.
Related identity layers
Review account control through crypto wallets and portability across Web3 social apps.