> 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/protocol/whitepaper/virtual-rollup.md). # Virtual Rollup #### Abstract The Virtual Rollup network enables participants to transfer rights to locked escrow through state transfers. Virtual Rollups are built on primitives VRC-1 through VRC-4 across two layers: the settlement layer and ZK State Channels. * VRC-1: ZKSC * Processes state transitions * VRC-2: Virtual Node * Handles communication between settlement layer and ZKSC * Ensures self-verification * Stores states * VRC-3: VIPE * Guarantees state is backed 1:1 against escrow * VRC-4: VIP * Supports permissionless capital flows Together, Virtual Rollups solve double-spend and counterparty risk. Double-spend is resolved through a common counterparty that interfaces with user. Full Self-Custody is guaranteed in spite of a malicious counterparty because users store state locally which can be redeemed for escrow on the immutable settlement layer. Consider the following attack scenario: The common counterparty cannot profitably collude with a fictitious user to withdraw escrow because VIPE funds require either: * universal consent of all relevant participants for immediate withdrawals * an onchain dispute process To attack the onchain dispute process, states must be * Valid: signed by both the participant and counterparty in the ZKSC * Exploitable: the Escrow-State difference reflected in a stale state exceeds the Escrow-State difference of the live state This scenario can occur when a participant’s balance genuinely decreased from its initial level before later recovering back to that same amount. Once the onchain dispute process is triggered, the participant's Virtual Node will automatically override with the valid, live state. If the participant is offline, another Virtual Node may execute the state proof on their behalf, earning the slashing reward. **Therefore, VIPE funds are inaccessible to malicious counterparties.** The VIP is not protected by an onchain dispute process and therefore could be drained by a malicious actor. But because the VIP definitionally represents unclaimed funds, it is already considered profit of the counterparty. #### Features * Trustless * Permissionless * Full Self-Custody --- # 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/protocol/whitepaper/virtual-rollup.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.