> For the complete documentation index, see [llms.txt](https://docs.vdex.trade/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vdex.trade/introduction/quickstart/technical-overview.md). # Technical Overview VDEX is powered by Virtual Rollups, a framework built on zero knowledge state channels. Transactions are self-validated and peer-to-peer, eliminating middle men and restoring power to users. Virtual Rollups segment capital into two layers: * The **settlement layer** is a blockchain that locks and reassigns **escrow** according to **state** * **ZK State Channels (ZKSC)** are primitives that let users reassign **escrow** rights through **state** transitions Participants lock funds on a settlement layer, like Ethereum, and receive a balance state. This balance state can be exchanged for position states through the ZKSC. At any time, users may submit states onchain to trustlessly unlock funds. This architecture has distinct advantages: * Privacy * Full Self-Custody * ZeroGas transactions * Sub-millisecond finality * Theoretically unbounded TPS Learn more in the VDEX whitepaper. {% content-ref url="/pages/bWeLJHg3EenlnhrvGEp8" %} [Whitepaper](/protocol/whitepaper.md) {% endcontent-ref %} --- # 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.vdex.trade/introduction/quickstart/technical-overview.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.