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. Web5 Interoperability

Why Web5?

PreviousCommunity PostsNextFuture Thoughts

Last updated 2 years ago

Was this helpful?

With the utilization of Platform, entities on the internet will be able to interact with others online without the need for trusted third parties. Without aggregators like Zion, s can still communicate with each other using for verification. This means data from a is still accessible even if certain services are down. It also allows for people to transfer data and create their own contracts without the need for a service to act as a middle man thanks to payments and verification.

As shown above, with the use of the Zion resolver (Or any resolver) for verification, s can send independently of any aggregator. This ends a prevalent problem in the digital age where businesses who rely on internet services to function are often forced to shut down when the services they use stop functioning. Since s are stored locally and in Master Replicas, entities can now to continue to function and have access to their data even if a service they use stops functioning. In addition, because of verification and decentralized storage, data has never been more secure. Data is no longer stored in a centralized cloud meaning an end to admin accounts with backdoor privileges into a user's data. This not only prevents the deletion of data from a centralized authority on a network, but it also prevents hackers from using exploits to gain access to all data on a network

Building on Web5

Thank you to the following contributors that helped bring this document together:

Almost any web application or service can be built utilizing for data storage, messaging, and verification. By adding decentralized payments with the the possibilities become endless. These are the pillars of the

In a Web5 future, almost all web services will utilize these features. With the use of verification there will no longer be a need for creating accounts on centralized networks to use services. Thanks to technology, any entity will be able to use their data in a variety of applications and services while still maintaining ownership. Additionally, the use of enables developers to create financial based services on Web5. This means everything from social media to even going on a vacation utilizing .

, , , , , Jason Charter, Evgen Scherbina,

πŸ’«
TBD's Web5 Decentralized Platform
Bitcoin Lightning Network
Zion Architecture
DID:ION
DWN
Bitcoin Lightning
Zion’s Web 5 Architecture
Liran Cohen
Daniel Buchner
Ryan Gentry
Justin Rezvani
Eric Ziouane
TBD's Web5
DWN
DID
DWN
Lightning
DID
DID:ION
DID:ION
DWN
messages
DWN
DID
Alice and Bob communicating on Web5
Zion Web5 Pillars
Plan Trip with Web5 Platform