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

# CUDIS Technology Infrastructure

The CUDIS Data Network is an advanced decentralized ecosystem designed to empower individuals to take control of their wellness data. It integrates blockchain, NFTs, and a secure processing infrastructure to provide a seamless platform for data ownership, rewards, and privacy preservation. The network consists of four key components: LDID for users’ holistic health data management with privacy protection, CUDIS Data Aggregator for creating unique, immutable records of health data, CUDIS DataHub for flexible and fair data transactions, and CUDIS Processing Nodes for transparent and efficient data processing.

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXfNNLilaRir4PSMtgA6RU7099YR7lt8rKSdSzdZF0n7DvDCvX425uKDhRM6n8uBRrjUnZMyo_3dtggrQC5gpvA9Zz1Vt5X8n4oNJE319ZHnPqq9PImnE57E-MtIIJ2ouk9YLaEv?key=aW7SilZuWgHSpqZtUAjZNuaH" alt=""><figcaption></figcaption></figure>

The four core components consists of:


---

# 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:

```
GET https://whitepaper.cudis.xyz/cudis-protocol/cudis-technology-infrastructure.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
