> For the complete documentation index, see [llms.txt](https://docs.wirexpaychain.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wirexpaychain.com/wirex-pay/wirex-pay-zk-infrastructure/zk-validium.md).
# ZK Validium
*\*DAC (Data Availability Committee)* is a trusted set of nodes that stores copies of data offline. The DAC is required to make the data available in the event of a dispute. Members of the DAC also publish on-chain attestations to prove that the said data is indeed available.
ZK Validium is another key component of Wirex Pay’s ZK tech stack. It operates similarly to ZK Rollups but stores data off-chain, which provides even greater scalability. Here’s how ZK Validium enhances Wirex Pay:
* Off-Chain Data Storage: By keeping transaction data off-chain, Validium can process a higher volume of transactions without burdening the main chain.
* Scalability: This method allows for virtually unlimited scalability, making it ideal for applications that require high throughput and low latency.
* Privacy: Like ZK Rollups, Validium uses Zero Knowledge proofs to maintain the security and privacy of transactions.
---
# 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://docs.wirexpaychain.com/wirex-pay/wirex-pay-zk-infrastructure/zk-validium.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.