LogoLogo
  • πŸ‘‹Introduction
    • Zion v2
  • πŸ—οΈZion Protocol Architecture
    • Overview
    • πŸ†”Decentralized Identifiers DIDs
      • DID Document
      • Service Endpoints
      • Sidetree
      • DID Universal Resource Identifier
        • Short Form URI
        • Long Form URi
      • DID Operations
        • Signing
        • Verification
      • Verifiable Credentials
    • βš™οΈDecentralized Web Nodes
      • Messages
        • Basic Message
        • Signed Data
        • Authorization
        • Encrypted Data
      • DWN Requests
    • ⚑Bitcoin Lightning Network
      • Invoices
      • Payments(HTLC)
      • Taro
        • Non fungible Assets
        • Assets
        • Multi-Hop Taro Transfers
        • Asset Exchange
  • πŸ“²Zion Social
    • Zion App
      • DID Account Creation
      • Social Profiles
      • Lightning Wallet
      • Creator Communities
      • Community Posts
    • Guide
  • πŸ’«Web5 Interoperability
    • Why Web5?
    • Future Thoughts
    • FAQs
  • πŸ“§Contact and Media
    • Contact Us
    • Social Media
Powered by GitBook
On this page

Was this helpful?

  1. Zion Protocol Architecture

Decentralized Web Nodes

PreviousVerifiable CredentialsNextMessages

Last updated 2 years ago

Was this helpful?

Most activities online between two entities require the exchange of messages and data. To make these exchanges, entities require an interface to store, discover, and fetch data related to the action an entity is participating in. A (DWN) is a data storage and message relay mechanism entities can use to locate public or private permissioned data related to a given . Decentralized Web Nodes are a mesh-like datastore construction that enable an entity to operate multiple nodes that sync to the same state across one another, enabling the owning entity to secure, manage, and transact their data with others without reliance on location or provider-specific infrastructure, interfaces, or routing mechanisms.

This allows anyone to build on the architecture, and utilize an entity's DWN for their applications and services. Almost any form of data can be stored on a DWN. Zion DWNs currently store data in the form of the following schemas (more to be added in the future):

All this data is stored locally on an entity’s personal devices and in remote locations Multi Master Replicas, which are highly available. Owners of a DWN choose what information is public or private. Permission access is resolved through DID authentication and object capabilities, which can only be given by the DWN owner.

This new form of data storage creates true ownership of one’s data and removes the single points of failure caused by centralized storage of data. Additionally, data on a DWN can only be edited or deleted by the DWN owner and those they give access to.

πŸ—οΈ
βš™οΈ
Decentralized Web Node
Decentralized Identifier (DID)
Zion
COMMUNITY
PERSON
POST
COMMENT
USER INTERACTION
IMAGE
VIDEO
DATETIME