You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: labs/lfdt/decentralized-directory-dedi.md
+9-9Lines changed: 9 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,18 +6,18 @@ grand_parent: Active Labs
6
6
---
7
7
# Decentralized Directory (DeDi)
8
8
9
-
# Short Description
9
+
##Short Description
10
10
The Decentralized Directory (DeDi) Protocol is envisioned as a global, interoperable specification for accessing public directories. It unifies access to public information published by registrars, regardless of the underlying technology or jurisdiction, providing a standardized, open-source protocol for real-time look-up of any public directory.
11
11
12
-
# Scope of Lab
12
+
##Scope of Lab
13
13
14
14
The goal of the DeDi Lab is to design, build, and validate a decentralized protocol and open-source reference implementation that enables real-time, global lookup of public registries. We're targeting both the common pain points of Gen‑1 to Gen‑3 directory systems and the fragmentation of APIs and data formats across jurisdictions. This lab will focus on robust architecture, developer tooling, and community adoption to establish trust infrastructure for digital identity, financial services, government directories, and other public‑good registries.
15
15
16
16
Our work will begin with a core protocol specification, defining URI and payload semantics (e.g., dedi://domain.com/registry-id/{record-id}), security mechanisms, and discovery patterns. This will include:
17
17
18
-
A modular, layered protocol stack that cleanly separates transport, registry metadata, schema validation, and cryptographic verification.
18
+
*A modular, layered protocol stack that cleanly separates transport, registry metadata, schema validation, and cryptographic verification.
19
19
20
-
Security and trust models, including signed directory manifests, integrity checks, revocation notifications, and key rotation workflows.
20
+
*Security and trust models, including signed directory manifests, integrity checks, revocation notifications, and key rotation workflows.
21
21
22
22
Once the specification is established, we'll produce a reference implementation in at least one languages (e.g., JavaScript) plus integration with common registries (e.g. company registrars, CA root stores). Key milestones include:
23
23
@@ -37,25 +37,25 @@ To drive adoption and interoperability, the lab will also:
37
37
38
38
* Coordinate with LF Decentralized Trust projects to align with DID, Verifiable Credentials, and decentralized identity ecosystems.
0 commit comments