Professional Documents
Culture Documents
Decentralized Web Platform - Public
Decentralized Web Platform - Public
Decentralized Web Platform - Public
LET’S GO >
Evolving the Web
In the current Web model, people are To create a new class of decentralized
users who do not own their data or apps and protocols (e.g. tbDEX) that
identity. They are given accounts by put individuals at the center, we must
companies and their data is held empower them with self-owned identity
captive in app silos. and restore control over their data.
2
WEB 2 WEB 3 WEB 5
,
The Decentralized Web Platform (DWP) enables developers to write Decentralized Web Apps (DWAs)
using Decentralized Identifiers (DIDs) and Decentralized Web Nodes (DWNs), returning ownership
and control over identity and data to individuals <-- We are calling this Web5
3
The Pillars of Web5
did://
Self-owned identifiers that Data formats and models for Data storage and message relay
enable decentralized identity cryptographic presentation nodes that serve as the
authentication and routing. and verification of claims. foundation for decentralized
apps and protocols.
4
Decentralized Identifiers (DIDs)
did:ion:1a2b3c4d…
{…} + {…} = {…} • No special utility tokens or subjective consensus
T0 TN Compiled
5
Verifiable Credentials (VC)
iss: did:example:bank
iss: did:example:bank
sub: did:example:alice
sub: did:example:alice
claims:
claims:
title: 12345678
acct: 12345678
name: Alice Smith
name: Alice Smith
+ issuer’s digital signature
+ issuer’s digital signature
+ subject’s digital signature
id: did:example:hardtron
verificationMethod: { JWK }
6
Decentralized Web Nodes
Universally Semantic
Addressable Discovery
Crawlable DID-relative Discover any form of published data
addressing of data Features simply by knowing its semantic type
Async Message
Replicated Threads
Masterless eventually consistent
replication of instances across Send and receive messages over a
devices and clouds DID-encrypted universal network
Supports any
Secure identity type
Data can be optionally encrypted
with an individual's DID keys Designed to support individuals,
companies, machines, or any other entity
Decentralized Web Nodes (DWN, DWeb Nodes) is an emerging standard for data
storage and relay that enables entities of any type (people, organizations, etc.)
to send and store encrypted or public messages and data, enabling a wide variety
of decentralized apps and protocols to be built on top.
7
The Anatomy of an Identity Wallet
Data
Management
Provide UI and functionality
to manage credentials and app DID Functions
data stored in DWNs
Support create, update, and
recovery of DIDs across all
supported DID Methods
Credential
Functions
Sign, verify, discover, and
present credentials to
verifying parties
Context
Management
Maintain and enforce which
DIDs are used with different
DID Auth people, apps, and services
Perform authentication and
manage authorizations (e.g. DWN
authz capabilities)
8
Web5 Network Topology
Alice’s Bob’s
remote DWN remote DWN
6 3
The combination of Decentralized Identifiers and Decentralized Web Nodes produces a Web of DID-secured
messaging, data sharing, and credential exchange that can replace one-off protocols (encrypted
messaging, photo sharing, etc.) with universal standards for all types of semantic data exchange.
9
Visualizing Web5 and the DWP Stack
DWAs
tbDEX, Other Apps
DWP
DWA Model
Decentralized Identifiers
10
Progressive Responsive Work Offline App-Like Fresh
11
From PWAs to DWAs
PWA DWA
+
Service DWN Service
Web App Web App
Worker SDK Worker
Decentralized
Centralized Web Node
App Server
12
Acme Bank? Is this legit?
1 2
DID Alice resolves the Bank’s DID Bank’s
Alice fetches credentials from the
Resolver Bank’s DWeb Node based on the schema Node
of the desired credential
navigator.did.request({
schema: “banking.org/charter”
})
13
tbDEX Message Threads
PFI 1
1 2
PFI 2 navigator.did.send({
schema: “tbd.website/schemas/bid”
navigator.did.send({ })
schema: “tbd.website/schemas/ask”
})
PFI 3
Alice’s local DWN
When viewed from 10,000 feet, tbDEX is a DWN-based threaded messaging and
data exchange protocol layer that runs atop the substrate of DIDs and
Decentralized Web Nodes.
14
Music to my ears
Alice’s remote DWN
1 2
Groove secures the ability to write TIDAL, which previously secured the ability
schema.org/MusicPlaylist objects to to read Alice’s schema.org/MusicPlaylist
Alice’s DWNs, and adds a new entry. entries, can read the entry Groove added.
navigator.did.store({ navigator.did.request({
schema: “schema.org/MusicPlaylist”, schema: “schema.org/MusicPlaylist”,
data: { ... } data: { ... }
}) })
Groove TIDAL
It’s not fun to regurgitate your playlists over and over again for
different music apps, so let’s stop doing that.
15
Hotel me your travel plans
Alice’s remote DWN
1 2
Alice grants her hotel, airline, and Alice can grant any app she chooses
rental car provider the ability to add access to reservations and tickets
schema.org/Reservation objects to her Travel App stored in her schema.org/Trip data
collection of trip-related data. to help her visualize her itinerary.
navigator.did.store({ navigator.did.request({
schema: “schema.org/Reservation”, schema: “schema.org/Trip”
data: { ... } })
})
Your preferences, tickets, reservations, and other travel data are strewn across
100s of different hotel, airline, and travel apps in a massive, unworkable mess.
DIDs + Decentralized Web Nodes can help unify these flows and experiences.
16
Web5 is a Decentralized Web Platform that
enables developers to leverage Decentralized
Identifiers, Verifiable Credentials, and
Decentralized Web Nodes to write Decentralized Always have been
We’re building an
app platform?
Follow: @TBD54566975
Chat: Discord
Contribute: GitHub