> For the complete documentation index, see [llms.txt](https://ncclabs.gitbook.io/ncc-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ncclabs.gitbook.io/ncc-docs/foundation-and-governance/ncc-foundation.md).

# NCC Foundation

The NCC Foundation is the long-term governance and coordination body of the NCC ecosystem. Responsible for ecosystem governance, Treasury coordination, protocol development, strategic partnerships, compliance frameworks and global ecosystem expansion.

## Why a Foundation as the Governance Entity

Public-infrastructure projects share a common challenge in long-term evolution: early stages are typically driven by a corporate entity, but as the ecosystem becomes open, multi-region and multi-jurisdictional, the legal, tax and governance limits of a corporate entity become bottlenecks. A foundation structure, centered on non-profit operation, long-term governance and ecosystem priority, is better suited to infrastructure projects that require openness, sustainability and regulatory flexibility.

The NCC Foundation's core responsibility is not to operate any single product in the short term, but to maintain NCC as long-term infrastructure: stable, open and sustainable. Operating under multiple regional compliance frameworks, the Foundation ensures that key decisions, asset management and protocol evolution rest on a solid legal and governance foundation.

## Four-tier Structure

NCC's governance structure consists of four independent yet collaborative entities. This layered structure is not redundant. It follows the principle of "separation of governance and operations, isolation of assets and protocol, parallel compliance and ecosystem."

<figure><img src="/files/WkeOgc6bbuKIn8tY5UUH" alt="Four-tier NCC governance: Foundation, Operating Entity, SPV Structures, Merchant &#x26; PayFi Network"><figcaption><p>Figure 4 · The four-tier NCC governance structure</p></figcaption></figure>

| 01 · Foundation                                                                                                  | 02 · Operating Entity                                                                                      | 03 · SPV Structures                                                                                                                      | 04 · Merchant & PayFi Network                                                                                                           |
| ---------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
| Governance Hub                                                                                                   | Protocol & Operations                                                                                      | Asset Compliance                                                                                                                         | Real-world Application                                                                                                                  |
| <p>Ecosystem governance and Treasury coordination.<br>Direction, key parameters, and cross-entity alignment.</p> | <p>Protocol development, technical evolution and product operations.<br>Accountable to the Foundation.</p> | <p>Compliance management and legal isolation for RWA assets.<br>Each asset class held by an independent SPV, isolated from protocol.</p> | <p>Onboarding of consumer scenarios, merchants and the PayFi network.<br>Operated independently to match regional commercial rules.</p> |

These four entities operate independently while being coordinated under the Foundation's governance framework. Enabling NCC to support asset compliance, protocol evolution, ecosystem expansion and global partnerships in parallel.

## Governance Principles

Long-term focus takes priority over short-term market volatility.

Multi-signature and tiered permission systems prevent single-point control.

Treasury operations, protocol upgrades and strategic partnerships are fully traceable on-chain or in documentation.

Continuous community participation is encouraged in governance processes.

Global compliance frameworks are combined with local-market adaptation.

## Treasury Management & Sources

The Treasury is funded from three main sources: protocol fees and ecosystem revenue generated by network operations; token reserves held by the Foundation; and partnership-driven and asset-allocation income from institutional collaboration.

Treasury usage centers on long-term ecosystem development. Primarily supporting protocol R\&D, liquidity, security audits, ecosystem partnerships, developer incentives, global market expansion and community growth. All major expenditures are executed via multi-signature and disclosed to the community on a regular basis.

## Path to DAO Governance

NCC's governance structure is not static. As the network matures, the Foundation will progressively open up governance in phases:

Foundation-led phase: in the early stage, the Foundation leads key decisions to ensure the protocol and asset framework are firmly established.

Hybrid Governance phase: community proposals, parameter governance and ecosystem councils are introduced; some decisions move on-chain.

Community-led phase: core protocol parameters, Treasury usage and strategic direction transition to on-chain DAO governance, with the Foundation taking a supporting role.

This evolution is not tied to a fixed timetable. It depends on ecosystem maturity. The Foundation will gradually open governance boundaries based on the quality of community participation, the maturity of governance tooling and the robustness of the protocol.


---

# 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://ncclabs.gitbook.io/ncc-docs/foundation-and-governance/ncc-foundation.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.
