> For the complete documentation index, see [llms.txt](https://spire-docs.gitbook.io/spire/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://spire-docs.gitbook.io/spire/based-stack/future-upgrades.md).
# Future upgrades
After the Based Stack launches and is ready for production use, the Spire Labs team will continue improving the rollup framework.
Some specific things we are thinking about:
* ZK Proof Aggregation / Shared Deposits: Enabling cheaper bridging between participating appchains. We are interested in collaborating with other teams on this.
* [Blob Aggregation](/spire/da-builder/blob-aggregation.md): Building tools to enable efficient sharing of blob space on Ethereum to minimize DA costs for lightweight applications.
* [A design to optimize blob space for appchains/rollups 🧵](https://x.com/Spire_Labs/status/1871421121264034289)
* Diverse Execution Environment / VM Support: Integrating and developing important features to support alternative VMs and next-gen execution environments natively.
* Realtime Proving: Enabling synchronous composability with Ethereum. We are looking into many designs related to this, including fast ZK proving and also TEE proving.
---
# 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://spire-docs.gitbook.io/spire/based-stack/future-upgrades.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.