Core Components of Web5
Web5 is built upon three fundamental components that enable decentralized identity and data management: Decentralized Identifiers (DIDs), Verifiable Credentials (VCs), and the Identity Overlay Network (ION). Together, these elements provide the technical foundation for self-sovereign identity, privacy-preserving data interactions, and secure, trustless ecosystems.
1. Decentralized Identifiers (DIDs)
What Are DIDs? A Decentralized Identifier (DID) is a unique, cryptographically verifiable identifier that enables self-sovereign identity. Unlike traditional identifiers (e.g., email addresses or usernames), DIDs are not tied to any centralized entity, giving users full control over their digital identity.
How DIDs Work
Creation: A user generates a DID locally, producing a pair of cryptographic keys—one public and one Example DID:
DID Document: Each DID resolves to a DID Document, a JSON-based structure containing:
Public keys for verification.
Service endpoints for interactions (e.g., credential issuance).
DID Document Example:
Anchoring: The hash of the DID Document is anchored to the Bitcoin blockchain via the ION protocol, ensuring immutability.
Updates and Deactivations: Users can update their DID (e.g., rotate cryptographic keys) or deactivate it entirely by submitting a new operation to ION.
2. Verifiable Credentials (VCs)
What Are VCs?
A Verifiable Credential (VC) is a cryptographically signed data structure that allows users to prove claims about their identity or data. These claims can be shared selectively, ensuring privacy and minimizing unnecessary data exposure.
How VCs Work
Issuance: An issuer creates a credential tied to the user’s DID and signs it using their private key.
Example VC in JSON:
Storage: The VC is stored off-chain (e.g., IPFS or Arweave), with its reference linked to the user’s DID Document.
Verification: A verifier (e.g., a dApp or DAO) requests specific claims from the user’s VC. Using cryptographic proofs, the verifier ensures the credential is valid and issued by a trusted entity.
3. Identity Overlay Network (ION)
What Is ION?
ION is a permissionless, open-source DID system built on Bitcoin. It operates as a Layer 2 protocol, enabling scalable DID operations without introducing new tokens or consensus mechanisms.
How ION Works
Batching Operations: DID operations (e.g., creation, updates) are grouped into batches and anchored as a single transaction on the Bitcoin blockchain.
Resolution: Applications resolve a DID by fetching its associated DID Document from ION’s decentralized network.
Benefits of ION:
Scalability: Batch processing reduces the number of Bitcoin transactions.
Immutability: Leveraging Bitcoin’s blockchain ensures tamper-proof identity records.
Decentralization: No central authority controls ION, making it resilient and trustless.
Bringing It All Together
These core components—DIDs, VCs, and ION—work together to create a framework for self-sovereign identity in Web5:
DIDs provide the unique identifier for a user’s digital presence.
VCs allow users to prove claims securely and privately.
ION ensures the integrity and trustworthiness of identity operations.
Web5 uses these components to redefine how individuals interact with the internet, enabling privacy-preserving, trustless interactions across decentralized ecosystems.
Last updated