Skip to content
NFH Fabric Support home
NFH Fabric Support home

Setting up the network environment

This section covers how a Network Facilitator Organization (NFO) sets up a new Fabric network using the Fabric Registry infrastructure on DeDi Global, and how approved Network Participants (NPs) are onboarded into that network.

A Fabric network is anchored by a verified namespace and one or more registries under that namespace. Together, the namespace and registry form the network's root of trust and define the network boundary that participants can use during signing, verification, and discovery.

Registering the network on Fabric

To register a new Fabric network, the NFO first creates its identity root on DeDi Global and then publishes a registry for the network. This registry becomes the canonical place from which participants in that network are referenced.

Dedi.global is a ready to use SaaS implementing the open DeDi protocol offered by the Network for Humanity Foundation. This allows registrars to effortlessly publish and manage their directories (aka public registries) on a decentralized, user controlled infrastructure.

What this establishes

  • A verified identity for the NFO, anchored to its domain

  • A registry that represents the network

  • A networkId that participants can rely on for trust and policy enforcement

The networkId is of the form:

<nfoDomain>/<registryName>

For example:

example-nfo.com/commerce-network

Tip: If you operate across multiple environments such as sandbox, staging, and production, create a separate registry for each environment. If needed, you can also create separate registries per sector. This keeps network boundaries explicit and allows participants to configure their ONIX instances appropriately to allow requests from networks they want to interact with. NFOs are free to create these boundaries as per their operational requirements.

Step 1: Set up a DeDi Global account

Create an account on DeDi Global.

Step 2: Create and verify the NFO namespace

  1. Create a namespace in DeDi.

  2. Request for whitelisting of a domain. This can be done here. The request will be processed within 5 minutes, provided no adverse signals are detected for the domain.

  3. Enter the domain name. A TXT record will be generated (only for whitelisted domains).

  4. Copy the generated TXT record as it needs to be updated in the DNS configuration file of your domain.

  5. Click “Verify” after you have successfully updated the domain’s DNS file. The DNS text propagation will take from 15 min to up to 48 hours. Once this is done, your domain is verified.

Example: If you as an NFO operate example-nfo.com, your namespace will be anchored to that domain.

Step 3: Create the network registry

Inside the verified namespace, create a new registry using the Fabric subscriber reference schema. This registry stores references to the NPs that belong to the network.

The registry name is significant because it becomes part of the networkId. For example, an NFO registry named commerce-network under example-nfo.com results in the network ID example-nfo.com/commerce-network.

Tip: You can create multiple registries for any number of boundaries that you want to create in the fabric. Based on your operational requirements you can create separate registries for specific environments or sectors that you are operating in.

Example: Suppose your verified domain is example-nfo.com

  • Sandbox environment: Registry name: sandbox Network ID: example-nfo.com/sandbox

  • Staging environment: Registry name: staging Network ID: example-nfo.com/staging

  • Production environment: Registry name: production Network ID: example-nfo.com/production

  • Sector-specific production environment: Registry name: mobility-production Network ID: example-nfo.com/mobility-production

Each network registry should eventually contain references to approved participants, with valid subscriber details, callback endpoints, and public-key material published by those participants in their own registries.

Powered by Plain