Digital identity is a digital representation of a person, organization, device, or software entity through identifiers and associated attributes within a particular system or context. It lets services recognize an entity and associate it with accounts, access rights, or transactions. It need not be globally unique, publicly named, or linked to a verified legal identity. One entity can have several digital identities, including pseudonymous accounts.
Identifiers, Attributes, and Credentials
An identifier references an account or subject, while attributes describe it. A username can act as an identifier; an age is an attribute. Neither an age nor a name is necessarily unique, and a username may identify different accounts in different services.
Credentials and authenticators serve related but distinct functions within a digital identity. A credential can support a claim about a subject or bind an authenticator to an account. An authenticator, such as a password or a cryptographic key, is used to demonstrate control during authentication. These elements do not all provide the same evidence about who or what an entity is.
How It Works
A service creates or accepts an account record, associates identifiers and attributes with it, and checks evidence when required. Identity proofing establishes confidence in a claimed identity, sometimes by checking documents or other evidence. It is not required for every service; some systems allow pseudonymous accounts without verifying a legal identity.
Authentication checks whether a claimant controls an authenticator associated with the account. Authorization then determines which actions are permitted, such as viewing a record or approving a transaction. A successful login therefore does not grant unlimited access. A digital identity supports recognition and access decisions, while the service's policies determine what evidence is sufficient and which permissions apply.
Looking for liquidity, exploring on-ramp/off-ramp services, or seeking expert guidance?
Get startedIdentity Management Arrangements
Identity management can use centralized, federated, or decentralized arrangements. These describe how responsibilities are assigned, not guaranteed security or privacy outcomes. Physical documents can supply evidence within any of these arrangements; they are not a competing digital architecture.
A centralized arrangement places management under one authority, while federation lets services rely on an identity provider's assertions. Decentralized arrangements can distribute control but may still depend on trusted issuers and verifiers. Centralized management does not require one physical database, and decentralization does not require all identity data to be distributed across blockchain nodes. Federation normally exchanges assertions rather than users' passwords. Cross-service use of a digital identity depends on compatible implementations and acceptance by receiving services. No arrangement automatically guarantees portability or complete user control.
Decentralized Identifiers and Verifiable Credentials
A decentralized identifier (DID) identifies a subject; it is not itself a verified claim about that subject. A verifiable credential carries issuer claims whose integrity and provenance can be checked. These technologies can support identity arrangements, but digital identity is not inherently blockchain-based. Neither requires personal information to be published on a blockchain. Where a ledger is used, its resistance to tampering does not establish the truth of the claims associated with an identifier or credential.
Trust, Privacy, and Control
Successful authentication shows control of an associated authenticator under the system's checks; it does not, by itself, establish a person's legal identity. Likewise, a valid cryptographic signature does not prove that every underlying claim is true. A verifier must consider the issuer, the evidence behind the claim, and whether the information is still applicable.
Impersonation, account compromise, excessive data collection, and linking activity across services remain relevant risks. Privacy depends on what is collected, disclosed, retained, and correlated. Verifiable credentials do not inherently conceal sensitive information, and practical user control depends on disclosure options, recovery processes, and the services involved.
Authentication and Disclosure Choices
Passwords, cryptographic authenticators and biometrics provide different forms of evidence and different failure modes. Multi-factor authentication combines distinct factor types rather than merely repeating one check. A biometric comparison can help unlock an authenticator but can produce errors and requires protection of sensitive biometric information. Strong authentication still needs safe recovery and protection against account takeover.
Digital signatures support checks on integrity and signing-key control. Selective-disclosure or zero-knowledge techniques may let a holder prove a limited statement without revealing every attribute, when the credential scheme and verifier support that technique. An ordinary verifiable credential does not automatically provide this property.
Encryption, access restrictions, limited retention, monitoring and user education can reduce exposure. Distributed storage, including systems such as IPFS, does not by itself make personal data confidential or safe to publish. Federation can concentrate operational risk at an identity provider, while decentralized arrangements retain dependencies on key custody, issuers, recovery mechanisms and compatible verifiers. Architecture labels therefore do not replace a concrete assessment of who can collect, read, change or correlate identity information.