> 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/use-cases/securitise-any-asset.md). # Securitising illiquid assets Provenance-anchored tokens for assets that don't move today. A warehouse of stored grain, a solar project's future cash flows, a plot of farmland, a fine-art piece, a batch of carbon credits — real value that sits frozen because the legal, custodial, and transactional plumbing to trade it isn't there. Every sale is a bespoke, lawyer-heavy deal; there is no continuous market and no cheap way to sell a fraction rather than the whole. NFH fabric supplies the **protocol-level plumbing** — verifiable provenance, custody, and transfer — so an issuer can wrap an asset once and let a fractional claim on it be discovered, priced, and settled on an open network. The legal and custodial wrappers remain the issuer's responsibility; what changes is that the technical friction no longer dictates them. ## What changes * **Illiquid assets become tradeable** without standing up a bespoke market venue for each class. * **Custody and provenance become cryptographic**, not documentary — the chain of ownership is signed and replayable rather than a folder of PDFs. * **Fractional ownership is a protocol pattern**, not a special legal structure — the legal wrapper still applies, but the plumbing no longer constrains what wrapper you can use. * **Price discovery reaches a wider pool** — a claim that used to require a broker's rolodex is discoverable by any qualified buyer on the network. * **Audit and compliance are continuous** — every transfer is anchored, so regulators and auditors see a live trail instead of a reconstructed one. ## Where to start Pick one asset class. Define the token class and the credential schemas for provenance, custody, and audit, then issue a test instrument on a sandbox tokenisation instance and run a fractional transfer between two holders. Most of the design effort goes into the credential schemas, not the token plumbing — so validate those with a custodian and a compliance reviewer before widening the asset set. --- # 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/use-cases/securitise-any-asset.md?ask=&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.