# Roadmap

**February 2024**

Virtual Rollup 1.0: The Trustless UX Update

* VR1.0 is a highly performant ZK State Channel with ZeroGas and Millisecond settlement
* VR1.0 transactions are validated directly by the user in their browser
* VR1.0 is integrated into partner GameFi DApps to test demand and stress-tech the tech
* **VR1.0 proves demand for better UX among users and DApps**

**August 2024**

Virtual Rollup 1.1: The DeFi Update

* VR1.1 supports new use cases, such as DEXes and other DeFi applications
* **VR1.1 will power VDEX**
* VR1.1 is a general-purpose ZK State Channel, not GameFi-specific

**September 2024**

Virtual Rollup 1.2: The Crosschain Update

* VR1.2 enables deposits from multiple chains to trade in one unified orderbook
* **VR1.2 = N chains, 1 orderbook**

**Q4 2024**

Virtual Rollup 1.3: The Unified Liquidity Update

* VR1.3 allows other perpDEXes and DeFi protocols to access one unified orderbook
* **VR1.3 = N DEXes, 1 orderbook**

**Q1 2025**

Virtual Rollup 2: The Industry Standard Update

* VR2.0 is EVM compatible
* **VR2.0 DApp integrations take 10 minutes, not 10 days. This dramatically reduces cost too**

**Q2 2025**

Virtual Rollup 2.1: The Multichain Update

* VR2.1 supports SVM, Cosmwasm, Ton VM, Near VM contracts
* **VR2.1 launches VDEX on Solana, Cosmos, Ton, Near and more**

**2026**

Virtual Rollup 3.0: The Omnichain Update

* VR3.0 allows Virtual Rollups to connect with each other so user can play new DApps without MetaMask interactions. Previously, changing DApps requires withdrawing and redepositing on the new Virtual Rollup
* VR3.0 completely abstracts blockchains and eliminates gas, creating the **“Virtual Experience”**


---

# Agent Instructions: 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://docs.virtuallabs.network/virtual-rollups/roadmap.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.