> 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-standards.md).

# Open standards

The open standards NFH fabric aligns with and contributes to.

NFH fabric is built from open standards, contributes back to them, and aligns with established work where it exists.

## Standards NFH fabric implements or aligns with

* **W3C Decentralized Identifiers (DIDs)** — pseudonymous identifiers across the Registry.
* **W3C Verifiable Credentials (VCs)** — Credentialling Edge issuance and verification.
* **BBS+ / SD-JWT** — selective disclosure of credential claims.
* **OpenTelemetry** — observability primitives across Observability & Audit.
* **x402** — HTTP-mediated value movement.
* **MCP (Model Context Protocol)** — agent-native discovery and service consumption.
* **BLAKE2** — cryptographic hashing and anchoring.
* **Open Policy Agent (Rego)** — network policy plug-ins for the Network Adapters Edge.

## Standards NFH fabric defines openly

* Beckn Protocol v2 — discovery, contracting, fulfilment.
* The federation protocol for cross-instance value movement.
* Namespace / registry / record schemas.
* Network adapter wire and plug-in formats.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.