> For the complete documentation index, see [llms.txt](https://maru-2.gitbook.io/maru/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://maru-2.gitbook.io/maru/maru-roadmap.md).

# Maru Roadmap

Plans and deliverables for next quarters:

#### Q3 2023

1. [Keccak benchmarks release](https://github.com/proxima-one/keccak-circuit-benchmarks/blob/master/short_description.pdf);
2. Basic Pools Volumes STARKs completion;
3. Maru [testnet](https://testnet.proxima.one/) 0.2 release (with Curve 3pool);

#### Q4 2023

1. Block hashes based Timeline for Proofs;
2. Maru testnet 0.3 release (with Curve, 1inch, Uniswap pools volumes proofs);
3. Aggregated STARKs (pre-calculate proofs and than use aggregation to combine them into final proof, saving lots of time);
4. Data SDK for Maru Proof Systems;

#### Q1 2024

1. dApp developers onboarding course;
2. Maru Mainnet Alpha release;
3. STARK-friendly internal storage (for big data proving);
4. Testnet Provers decentralization;

#### Q2 2024

1. Maru ZKVM release;
2. DeFi projects onboarding;
3. Maru Proving Network Mainnet release;

#### Q3 2024

1. Other EVM chains support (Polygon, BSC, Avalanche);
2. Data interoperability (query, compute and proof data with verification in other chains);
3. Data Proofs for Cosmos SDK testnet release;

#### Q4 2024

1. Data Proofs for Cosmos SDK Mainnet release;


---

# 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:

```
GET https://maru-2.gitbook.io/maru/maru-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.