Decentralized Web Node

Decentralized Web Node (DWN) is a decentralized data storage and message relay specification that enables entities to store, discover, and exchange data using Decentralized Identifiers (DIDs). Developed by the Decentralized Identity Foundation (DIF), DWNs create a mesh-like datastore that allows entities to operate multiple synchronized nodes for managing and transacting data without relying on centralized infrastructure.

The specification provides a standardized way for entities to:

• Store and manage both public and private permissioned data
• Exchange messages and credentials securely
• Maintain data sovereignty through self-hosted nodes
• Sync data across multiple nodes seamlessly
• Control access through granular permissions

Key differentiating features include:

• Protocol-based data organization using declarative rules
• Multi-node synchronization capabilities
• Encryption at the individual message level
• Flexible permission models for data access control
• DID-based authentication and authorization

Technical Analysis:

1. Purpose and Scope:

• Provides decentralized personal and application data storage
• Enables message relay between entities
• Supports credential, app, and service data flows
• Facilitates DID-based data discovery and access

2. Key Technical Specifications:

• Component Layers:
  • DID Authentication
  • Access & Authorization
  • Interface Definitions
  • Object Format
  • Object Signing/Encryption
  • IPLD Multiformats

3. Implementation Requirements:

• Must support core interfaces:
  • Records for data storage
  • Protocols for defining rules
  • Sync for node synchronization
  • Permissions for access control
• Must implement specified encryption schemes:
  • ECIES-ES256K with AES-CTR
  • X25519 with AES-GCM
  • X25519 with XSalsa20-Poly1305

4. Security Considerations:

• Message-level encryption
• DID-based authentication
• Granular permissions system
• Protocol-based access control
• Key derivation schemes for encryption

5. Interoperability Features:

• Standardized message formats
• Common protocol definitions
• Shared schema support
• Cross-node synchronization
• Standard encryption formats

6. Current Adoption Status:

• Status: Draft specification
• Active development within DIF
• Reference implementation in progress
• Community feedback incorporation ongoing