> For the complete documentation index, see [llms.txt](https://digard.gitbook.io/digard-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://digard.gitbook.io/digard-whitepaper/core-components/how-digard-works.md). # How DIGARD Works **DIGARD Cube** **DIGARD Cube** acts as the foundational infrastructure for developers and users, providing a modular system for off-chain interaction. Its design ensures scalability and reliability, offering developers flexibility in deploying their projects. With **Cube**, developers can seamlessly manage assets, implement tokenomics, and interact with various chains. The Main goal of the Cube is collecting off-chain DATA. **DIGARD Crawler** **DIGARD Crawler** is a high performance chain indexer that enables real time data retrieval and organization across all supported blockchains. With the current compatibility across all EVM chains and plans to support Non-EVM chains soon, **DIGARD Crawler** empowers developers to deploy NFT based reward systems or tokenized assets in minutes. Integration of new EVM chains can be completed in a matter of days, offering unparalleled flexibility for growing projects. The main goal of the Crawler is collecting on-chain DATA. **DIGARD Reactor** **DIGARD Reactor** simplifies the process of deploying and scaling blockchain based applications. Reactor collects DATA from Cube and Crawler, turns the data into valuable output. It streamlines interactions between chains, allowing developers to focus on building their projects without worrying about underlying complexities. **Reactor** ensures secure, automated, and efficient execution of tasks like asset tokenization, staking mechanisms, and reward systems. --- # 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://digard.gitbook.io/digard-whitepaper/core-components/how-digard-works.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.