DeDi: Decentralized Directory Protocol
An open protocol for public, machine-readable trust infrastructure — verifiable participants, keys, memberships, and revocation across any ecosystem.
Get started in 10 minutes View on GitHub
What problem does DeDi solve?
Most trust systems can verify signatures. What they struggle with is the step before verification: discovering the right authoritative registry, retrieving current public state, and applying it consistently across different registries.
DeDi provides a common protocol and schema surface for that operational trust layer.
If your system needs to know which public key to trust right now, whether an entity is still authorized, or which registry is authoritative for a namespace — DeDi is built for that.
Choose your path
| I want to… | Start here |
|---|---|
| Build a verifier or resolver | Quickstart → Build & Integrate |
| Operate a registry | Operator Guide |
| Evaluate DeDi for adoption | Adoption & Conformance |
| Understand the protocol | Core Concepts → Architecture |
| Propose a change | Protocol Change Process |
Available schemas
| Schema | Purpose |
|---|---|
public_key |
Current and historical public key material for signature verification |
revoke |
Revocation and deny-list entries |
membership |
Public membership and affiliation state |
endpoint |
Service endpoint advertisement |
Beckn_subscriber |
Beckn participant directory entries |
Beckn_subscriber_reference |
Federation and delegation reference records |
What DeDi is (and isn’t)
DeDi is a protocol and schema layer for public directories, an interoperability approach for lookup and trust discovery, and a foundation for multiple ecosystems.
DeDi is not a single hosted product, a blockchain requirement, or a substitute for governance and assurance.