> For the complete documentation index, see [llms.txt](https://docs.nfh.global/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nfh.global/nfh-fabric/open-rails.md).

# Why do we need an open NFH fabric?

## The cost of the world we have

Closed value rails are expensive, and the bill is measurable:

| **$2.5T**     | Trade financing requested and refused — verifying the deal costs more than the deal earns. *(ADB, 2025)*                        |
| ------------- | ------------------------------------------------------------------------------------------------------------------------------- |
| **$5.7T**     | Credit small businesses need and cannot get — real order books, invisible to capital. *(IFC–World Bank, 2025)*                  |
| **up to 15%** | Skimmed from a worker's remittance, because intermediaries each re-run the same checks. *(World Bank, 2025)*                    |
| **15–30%**    | The toll a walled garden takes from the seller inside it, for matchmaking alone — and the reputation earned there cannot leave. |
| **2–5 days**  | To settle a cross-border business payment. The message crosses the world in milliseconds; the money does not.                   |

These are not failures of capital or technology. They are failures of **coordination** — the tax a world pays when it has no shared, neutral ground for trust, discovery, and settlement, so every market builds its own privately and charges rent. That tax falls hardest on the smallest, poorest, and youngest.

## The shift already underway

Intelligence is moving the economy from **platform-centric** to **network-centric**:

| Platform-centric                     | Network-centric                      |
| ------------------------------------ | ------------------------------------ |
| Walled — closed to outsiders         | Open — anyone can join               |
| Human-paced — paperwork & delay      | Agent-paced — instant & programmable |
| Few & large — high-value, low-volume | Many & tiny — low-value, high-volume |

The economy must soon coordinate **a billion-plus** businesses transacting directly, **a trillion-plus** autonomous agents acting on their behalf, and micro-transaction volumes on the order of **a million times** today's. No system built for the platform era survives contact with those numbers. The toll-taking intermediary — viable when transactions were few and large — becomes a tollbooth on every drop of a flood.

## Proof is the hinge

When agents transact a trillion times a day, trust must be **cryptographic, programmable, and instant**. That requirement has four faces, and NFH fabric provides all four:

| Face               | What it means                                                                          | NFH fabric service                                                                                                                      |
| ------------------ | -------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
| **Trust**          | Verifiable identity for humans, entities, and agents.                                  | [Registry](/product-documentation/products/registr.md) · [Credentialling Edge](/product-documentation/products/vc-on-edge.md)           |
| **Controls**       | Granular permissions and consent — an agent does exactly what it was authorised to do. | [Credentialling Edge](/product-documentation/products/vc-on-edge.md) · [Network Adapters Edge](/product-documentation/products/onix.md) |
| **Accountability** | An immutable trail linking every action to an identifiable actor.                      | [Observability & Audit](/product-documentation/products/observability-audit.md)                                                         |
| **Liability**      | A clear chain of responsibility when something goes wrong.                             | [Observability & Audit](/product-documentation/products/observability-audit.md) · [Pincer](/about-nfh-offerings/readme.md#pincer)       |

Strip these away and the agent economy is a fraud engine. Build them in, and it becomes the most inclusive market in history.

New rails *will* be laid in the next few years, and they will then last for generations. Exactly one thing is not yet decided: **whether those rails are open or owned.**

* **Owned.** Gatekeepers. A toll on everything. Power concentrates.
* **Open.** Build freely. Value to the edges. A commons, like the internet.

NFH fabric is NFH's answer: an open layer for value, so the gains of the intelligent era reach billions at the edges instead of whoever builds the wall.

***

*Sources: ADB Global Trade Finance Gap Survey 2025 · IFC–World Bank MSME Finance Gap Report 2025 · World Bank Remittance Prices Worldwide 2025.*


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.nfh.global/nfh-fabric/open-rails.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
