> 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/about-ncc/project-introduction.md). # Project Introduction ## What is NCC NCC is a Web3 infrastructure project built around RWAs, on-chain liquidity and consumer-application networks. It is not defined as a single trading platform, GameFi application or payments tool. It is a value network composed of multi-layered protocols and application scenarios. Within this network, real assets are transformed into verifiable digital assets through compliant structures and on-chain technology. These assets enter the Unified Liquidity Engine to gain circulation capability and price-discovery mechanisms. Users access digital assets through the Marketplace, PayFi and other applications. Consumer behavior, identity data and ecosystem participation are recorded in the NCC Identity Layer, forming user reputation and access permissions over time. NCC extends Web3's core capabilities beyond asset issuance and trading into real-asset circulation, consumer participation and identity coordination. The long-term direction is to evolve Web3 from an asset-trading network into infrastructure for the real economy. ## Why Now After multiple market cycles, tolerance for narrative-only projects, inflationary incentives and short-term liquidity speculation has clearly declined. Institutions and users now focus on asset provenance, verifiable yield, compliance pathways, real applications and long-term governance capability. The rise of RWAs reflects an accelerating connection between blockchain and traditional finance, asset management and commercial scenarios. At the same time, PayFi, on-chain identity, consumer rights and cross-chain liquidity are becoming essential foundations for real-world Web3 adoption. Against this backdrop, NCC integrates real assets, liquidity and real-world applications into a unified system. NCC's design principle is to start from real demand, not from token issuance alone. The project first asks: Are the assets real? Is the yield verifiable? Is liquidity sustainable? Do users have real use cases? And can the governance structure support long-term evolution? On this basis, NCC positions itself as a connection layer: connecting real-world assets with on-chain markets, consumer behavior with digital rights, user identity with ecosystem access, and foundation governance with open-network development. --- # 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/about-ncc/project-introduction.md?ask=&goal= ``` `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.