> For the complete documentation index, see [llms.txt](https://mzf-protocol.gitbook.io/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mzf-protocol.gitbook.io/whitepaper/mzf-protocol-white-paper.md).

# MZF PROTOCOL White Paper

## Executive Summary

MZF PROTOCOL is a decentralised capital deployment platform purpose-built for Pre-TGE ventures, with a central focus on token rights loans. The protocol operates across three primary alternative financing verticals — DeFi-enabled loans, mezzanine debt, and venture debt — each assessed on a case-by-case basis depending on the startup’s growth profile, capital structure, and projected token economics.

At the core of the ecosystem is $MZF, a fixed-supply utility token that enables access to staking incentives, deal participation, and gated community tools. Unlike equity-linked or yield-bearing tokens, $MZF does not confer ownership or revenue rights. Its value lies in utility — empowering users to signal support for vetted opportunities, earn protocol incentives, and unlock ecosystem features.

All staking rewards are distributed from a fixed token reserve within the 500 million $MZF supply cap, with a halving mechanism every four years. This design encourages early adoption, long-term alignment, and predictable incentive dynamics, echoing the sustainable issuance model pioneered by Bitcoin.

Key features of the MZF PROTOCOL platform include:

1. On-Chain Payment Rail for RWA Deployment: MZF PROTOCOL provides a blockchain-native payment infrastructure purpose-built to deploy capital into real-world assets (‘RWA’) via:
   1. Token Rights Loans;
   2. Revenue-Based Financing; 
   3. Mezzanine Financing; 
   4. Venture Debt;
   5. Fixed-Term Loans; and
   6. Convertible Debt.
2. Smart Contract Settlement & Access Control: Transactions are executed via smart contracts, automating fund disbursement, milestone-based releases, and KYC-gated access for verified participants.
3. Transparent Flow of Funds with Auditable Trails: All capital movements — from treasury to borrowers — are transparently recorded on-chain, enabling real-time auditability and minimising counterparty risk.
4. Direct Funding Access for Startups via dApp: Verified Pre-TGE ventures (or Startups at any other stage) can submit funding requests directly through the MZF PROTOCOL dApp, including deal terms, token rights mechanics, and collateral details. This digitised underwriting funnel connects startups with capital in a lean, programmable manner.

Through this combination of token-based incentive design, smart contract automation, and real-time financial transparency, MZF PROTOCOL bridges the gap between DeFi and traditional credit markets. By offering an alternative debt capital stack tailored for Web3-native startups, it enables broader access to non-dilutive funding while maintaining a scalable and compliant protocol architecture.

## Quick links

{% content-ref url="/pages/8AiZ5YAmwRJlWOOVEk6U" %}
[What we do](/whitepaper/overview/what-we-do.md)
{% endcontent-ref %}

{% content-ref url="/pages/jSwXpNV10GCmytri58eR" %}
[Roadmap](/whitepaper/overview/roadmap.md)
{% endcontent-ref %}

{% content-ref url="/pages/ZJ40wJsDHPEqBYvx5THV" %}
[Tokenomics](/whitepaper/overview/tokenomics.md)
{% endcontent-ref %}


---

# 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://mzf-protocol.gitbook.io/whitepaper/mzf-protocol-white-paper.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.