What is WEB5 about, and why does it matter in the post-AI and post-blockchain world?
The ultimate challenges of modern WEB
- internet were born without an identity layer. So you don't know with whom you talk
- internet was born stateless. So it is allowed to scale massively, but how user keep his data?
- How to prove data ownership and authentisity of data ?
Why does it matter now in the AI world?
AI will reshape a landscape completely. We will need a way to identify original content from a generated one. Data is the main fuel of AI models. Research shows that evem smaller models perform better on quality data. it is opens topic of data economy and data ownership. Even more now, we are extending our self with an agent — now we need to manage agent identities and payments for interconnected agents network. All this requires new ways of managing identity and data ownership
WEB3 gives you Assets to own but …
We all know about Web3 and blockchain, together with a programmable economy and tokenization of assets. Web3 was invented as a concept by Dr.Gavin Wood from Ethereum blockchain to sell an idea of smart contracts and Ethereum network. The biggest value of this movement was a ownership. First time we got a mechanism to give a user digitalised assets that user could own together with it we faced with a problem of identity in a decentralized world. To get deeper historical and technological read my article Pre Web , Web1, Web2 , web3 , web5 , web7 and all hundreds of future web X explained in 12 Toots
Challenges of WEB3
- Everybody has his view on the web3 future and his own set of challenges
- Privacy is broken and now we have a tornado and all Layer 2 / layer 3 patches that broke a ladger concept
- The user is locked in a particular blockchain and practically has no way of interacting ouside of network
- Networks of Networks — only one god know how many of blockchains and crypto currency procects we have nowadays
- data persistence is limited and expencive
Web 3 and second system syndrome
We have so many requirements and features for the next web version that we failed to deliver it and got lost.
- Internet for machines and semantic web
- internet of connected data
- internet of IoT devices and things
- Internet of identity and ownership and most recent challenge Internet of AI-powered agent Satohi paper and Vitalic Buterin idea of intelligent contracts bring a new view of ownership and economy but ignore heavenly privacy , ownership, and data.
Web3 locks a user in a new glass cage
Blockchain is a promise of WEB3 and a new era of internet lock users in even more restricted and isolated networks that force to be self-contained and accumulate mainly public data inside a network with highly high-cost storage and require the cost of interaction. Another challenge is a speed of transition — blockchains are slow. So, blockchain is cool for assets and a new economy but fail to create an identity and new social space for extended human and machines.
WEB5 builds on top of Self Sovereign Identity
For SSI read my article Self Sovereign Identity in 7 Toots . The idea is simple — we build a missed identity layer that treats humans as more than a private key and gives tools to create a data point about ourselves and others and freely exchange this data via protocols. We unlock a user from a glass cage of blockchain and a fragmented nightmare of web2 platforms and apps where you slice yourself to hundreds of you. Now holistic, you open to the world.
Building Blocks of WEB5
- Identity layer on top of SSI tools — DIDs
- missed decentralized persistence layer with permissions and synchronization on top of DWN
- Verifiable and Owned data with Verifiable Credentials
- DApps on top of DWNs
Old WEB3 & SSI Tools
Asymmetric Keys + Signatures — the backbone of decentralized identity in #web3 and #web5 that give #algorithmic #cryptographical basics of identity. But while we not locked to a network that creates addressable space, we have a new challenge — How to distribute and manage Public Keys, so we have a need of DPKI — decentralized Public Key Infrastructure.
DID give Decentralized Public Key Infrastructure that distributes your Public Keys and service endpoints to a broader audience.
DID is a core of SSI and creates a cryptographic verifiable, decentralised, resolvable identifier. A decentralized Identifier (DID) is a unique, persistent, and cryptographically verifiable identifier allowing individuals, organizations, or devices to independently establish and manage their digital identities. DIDs are used in decentralized identity systems, enabling users to have control over their data and interact securely without relying on a centralized authority.
Representation of did itself. is a part of DID URI.
A DID (Decentralized Identifier) document is a structured, machine-readable JSON or JSON-LD document that contains essential information associated with a specific DID. It serves as a “public profile” for a decentralized identity, providing the necessary details for verifying signatures, encrypting/decrypting messages, and interacting with the identity’s associated services.
The DID document typically includes:
- The DID itself: A unique identifier that represents the decentralized identity.
- Public keys: One or more public keys associated with the DID, used for cryptographic operations such as verifying signatures and encrypting messages.
- Authentication methods: Mechanisms to prove control of the DID, which typically involve the use of public keys.
- Service endpoints: URLs or other identifiers of services related to the DID, such as profile information, communication channels, or data repositories.
- Other metadata: Additional information related to the DID, such as timestamps, controller information, or specific DID method details.
The DID document’s information allows other parties to trust and interact securely with the associated DID without relying on a centralized authority. DID documents are created, updated, and deactivated according to the rules and processes defined by the DID method associated with the DID. They are usually stored on distributed ledgers, blockchains, or other decentralized networks, making them globally resolvable and cryptographically verifiable.
It is four possible DID Actions.
- Creating a DID: Generating a new identifier and associating it with a DID document containing public key material and service endpoints for the identity. For DIDs on Blockchain, we could see term Anhoring. DID anchoring refers to registering a Decentralized Identifier (DID) and its associated DID document on a distributed ledger or blockchain. Anchoring provides a secure, tamper-proof, and verifiable record of the DID’s existence and its associated information, making it an essential component of decentralized identity systems.
- Resolving a DID: Retrieving the DID document associated with a specific DID, which is essential for verifying signatures, encrypting/decrypting messages, and interacting with the identity’s associated services.
- Updating a DID: Modifying the DID document, such as adding or updating public keys, service endpoints, or other metadata. This action typically requires authorization from the DID controller.
- Deactivating a DID: Marking a DID as inactive, rendering it unusable for future interactions. This action also usually requires authorization from the DID controller. DID resolution is a primary and mandatory operations. Every method has a created procedure.
The method is the concrete implementation that defines the rules and processes for did actions on a particular distributed ledger, blockchain, or other decentralized network. DID methods provide a standardized way to manage DIDs and their associated DID documents, enabling interoperability between decentralized identity systems. Each DID method is identified by a unique method name, which appears in the DID itself. For example, a DID with the method name “example” would look like “did:example:123456789abcdefghi”.
ould change an owner and be sold or reasigned
DID Relations demystified
Relations between all parts of DID identifier can be illustrated in the following diagram. DID method dictate how DID identifier gets created, updated, deactivated, and resolved.
DWN — Missed data Layer of internet
DWN = Secured storage + message relay. Yep, it is similar to nostr relays but focused not on social media but data and data exchanges. It is more complex because it should be more generic and allow you to describe complex data and data interactions. That is why DWN as a protocol allows you to describe your own protocols around a data.
Protocol-based on messages, but it is not about messages at all. Messages only transfer data about Records, Permissions, Hooks, and Protocols.
DWN is a stack of Access and data Protocols.
Key Concepts and Interfaces
- Schema — the core of interoperability defines a data context and meaning.
- Records — the interface of Decentralized Web Nodes provides a mechanism to store data relative to shared schemas.
- Permissions — provides a mechanism for external entities to request access to various data and functionality. It employs a capabilities-based architecture that allows for DID-based authorization and delegation of authorized capabilities to others if permitted by the owner of a Decentralized Web Node.
- Protocols — introduces a mechanism for declaratively encoding an app or service’s underlying protocol rules, including segmentation of records, relationships between records, data-level requirements, and constraints on how participants interact with a protocol. With the DWeb Node Protocols mechanism, one can model the underpinning protocols for a vast array of use cases in a way that enables interop-by-default between app implementations that ride on top of them.
- Hooks — aim to not only allow permissioned subscribers to be notified of new data but also optionally respond to the entity’s request that triggers their invocation. This allows a subscribed entity to process the data and react to the entity waiting on results.
Verifiable credentials allow you to share information about yourself and others in a temper-proof and end-verifiable way. VC contains the issuer’s signature, a person, and an organization that creates a data statement. Critical part it is based on open standards
Anatomy Of VC
- Machine-readable data context for semantic web and AI
- optional schema
- optional revocation data
- optional expiration date
VC = data + metadata + signature
Example of Revocable VC
type: [ 'VerifiableCredential', 'ContentLike' ],
Spec NOSTR events is verifiable data, too as far as it is signed
DApps — How it works all together
It is similar to a WEB3 Dapp, but istead of blockchain it is connected to several DWNs that manage and store the data of applications or particular user represented by DIDs. Web5 Dapps is designed more for human interaction gateways that give you a UI etc. DWNs and message interfaces are used with application-level protocols for agent or wallet-to-wallet interactions.
Web5 gives identity and persistent layers missed by the web in a network-agnostic manner. It could work on top of regular network protocols or local
- DID — give you a distribution of Public identities that are network network-independent
- DWNs — give a persistent and interaction layer
- DWNs protocols — allow definition Dapps data exchange logic.
- VCs allow to add ownership and authenticity of data and build data and agent economy on top of it
- Dapps — use all these tools to interact with a human in a loop. Serve a UI and interact with DWNs and agents.