Skip to content
NFH Fabric Support home
NFH Fabric Support home

REGISTR — build trusted networks

Digital ecosystems across sectors—commerce, mobility, energy, sustainability, public services, and more—need a reliable way for participants to identify, authenticate, and communicate with each other.

Executive Summary

Digital ecosystems across sectors—commerce, mobility, energy, sustainability, public services, and more—need a reliable way for participants to identify, authenticate, and communicate with each other. Today, this often requires custom integrations, manual key exchanges, or sector-specific directories that don't scale.

The Fabric Registry Service, built on the DeDi Global infrastructure, an implementation of the Decentralized Directory Protocol (DeDi), provides a verifiable identity directory for any Fabric-enabled participant. It enables organizations of all types to publish network identity under their own domains, ensuring trusted addressability and interoperability across Fabric-based networks.


1. Why the Registry Service Matters


The Problem Today

Many facilitators and network operators maintain their own directories of participants. As networks expand, keeping these directories in sync, verifying identities, and updating configuration data becomes increasingly complex.

Because each directory is independently operated, they naturally become isolated, making cross-network interaction more difficult.

The Fabric Registry Service provides a shared, protocol-aligned foundation for publishing identity information while allowing facilitators to continue curating and governing their networks as they always have.

2. The Fabric Approach

The Registry Service provides:

  • ✓ Global Addressability — Every Fabric-compatible participant gets a resolvable, protocol-standard identity under a verified namespace—making it straightforward for entities to reference, validate, and interact with one another.

  • ✓ Self-Owned Identity Records — Participants publish their own subscriber information under their own domain, ensuring autonomy and reducing duplication across registries.

  • ✓ Cryptographic Trust Without Manual Effort — Public keys, domain proofs, and signing details are published in a consistent, verifiable format. This removes the need for custom key exchanges or facilitator-specific trust setups.

  • ✓ Seamless Integration with ONIX — ONIX automatically retrieves subscriber details during transactions. No additional registry APIs, integrations, or onboarding workflows are needed.

The result is a simpler, more coherent technical foundation that empowers facilitators while strengthening the entire network.


3. What the Registry Service Enables


a. Global Addressability

A uniform, protocol-defined way to reference participants across ecosystems—regardless of sector or facilitator.

b. Verifiable Trust Layer

Domain-anchored identities ensure:

  • Authenticity

  • Key validation

  • Signed request verification

All without manual coordination.

c. Structured Subscriber Data

Standardized schemas for:

  • Subscriber ID

  • Callback URLs

  • Domain codes

  • Network roles (consumer/provider node/CDS/etc.)

  • Public keys

Ensuring compatible, predictable integrations.

d. Facilitator Support

Facilitators can publish Subscription Reference Directories — curated sets of participants — while relying on the registry service as the technical backbone for addressing and validation.

e. Seamless Interoperability with ONIX

ONIX automatically:

  • Retrieves subscriber information

  • Fetches keys

  • Performs signing and verification

Allowing participants to transact smoothly without extra integration steps.


4. Key Benefits

Beyond the capabilities above, the Registry Service is also:

  • ♻️ Applicable Across Sectors — Suitable for commerce, mobility, health, energy, sustainability, public services, and any domain adopting Fabric.

  • 📈 Proven to Scale — In the latest performance testing, the Registry Service handled datasets ranging from 100,000 to 1.5 million records while sustaining around 1,000 requests per second on modest infrastructure. In larger configurations, it scaled to over 2,200 requests per second with p95 latency of about 42 ms, demonstrating strong performance for high-volume, low-latency network workloads.


5. Who Should Use This Service

  • Organizations Building Fabric-Enabled Systems — Across any sector — energy, mobility, sustainability, commerce, public services, etc.

  • Developers — Implement Fabric flows without managing discovery, key-exchange setups, or custom integrations.

  • Facilitators & Network Operators — Curate and govern networks with ease, without carrying the full technical maintenance burden of identity/addressability infrastructure.

  • Enterprises & Agencies — Standardize trust and identity across wide-ranging digital ecosystems.


6. How It Works

  1. Namespace Creation — Create and verify domain ownership to establish an identity namespace.

  2. Registry Publication — Add a registry to list beckn subscriber details.

  3. Subscriber Record Creation — Publish callback URL, roles, domain codes, and public keys.

  4. ONIX Interaction — ONIX automatically resolves subscriber details during network interactions.


7. Typical User Journey

  1. Create & Verify Namespace — Prove domain ownership and establish your identity namespace.

  2. Add a Registry — Publish a registry following the Fabric subscriber schema.

  3. Add Subscriber Records — Include your callback URLs, roles, domain codes, and keys.

  4. Transact through ONIX — Start participating in Fabric interactions with automatic address resolution and trust validation.


8. Glossary

  • Namespace: A verified identity space tied to an organization's domain and used as the root of trust for publishing participant information.

  • Registry: A list of subscriber records under your namespace.

  • Subscriber Record: The specific values describing how a participant can be addressed and authenticated—such as URLs, roles, domain codes, and public keys.

  • Facilitator: An entity that curates and governs networks using Fabric standards.

  • Domain Code: Represents a domain like mobility, commerce, energy, or sustainability.

  • ONIX: An enterprise-grade middleware adapter that enables seamless communication in Fabric-enabled networks by handling routing, key retrieval, and validation.

  • DeDi Global: Infrastructure implementing the Decentralized Directory Protocol.


9. Get Started

📘 User Guide

If you are a Network Facilitator Organization (NFO) and want to set up a new Fabric network, create a registry, and onboard participants — Setting up the network environment

If you are a Network Participant (NP) and want to register your subscriber details on the fabric — Registering on the fabric

💬 Need Help?

Raise a support ticket here.


The Fabric capability: Registry

REGISTR realises the Fabric Registry — a decentralised, verifiable directory of who's on the network: people, businesses, agents, instruments, schemas, and the public keys that prove them.

What it gives you

  • Pseudonymous identifiers — names that resolve to DIDs, with versioned, signed records.

  • Public keys — cryptographic material for verifying signatures and credentials.

  • Namespaced registries — domain-scoped lists (e.g. licensed assayers, accredited issuers, certified providers).

  • Delegations — fine-grained authority transfer between identities.

  • Cryptographic anchoring — every record proven, every change auditable.

Where it sits — a service NFH runs (the central, globally-addressable registry surface) plus the protocol NFH defines (the namespace / registry / record model and the publish / lookup / delegation API).

Standards alignment: W3C DIDs · BLAKE2 hashing · open API specifications.



Powered by Plain