> 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/execution-environment-virtual-machine.md).

# Execution environment / virtual machine

<figure><img src="/files/bdg8ve78DiNA0K1ZeUN0" alt="Banner image"><figcaption></figcaption></figure>

One of the important primitives in the Based Stack is the separation of sequencing and execution.

<table><thead><tr><th width="144"></th><th></th></tr></thead><tbody><tr><td><strong>Sequencing</strong></td><td>Coming to consensus on the inputs to a State Transition Function (STF).</td></tr><tr><td><strong>Execution</strong></td><td>Coming to consensus on the output of an STF.</td></tr></tbody></table>

At Spire, we group concepts like validity proofs (aka ZK proofs) and fraud proofs, but also virtual machine (VM), which is what we will focus on in this section. We believe that developers should be able to choose the virtual machine that works best for their application.&#x20;

> The Based Stack is designed to eventually support multiple VMs.

We are especially interested in combining the throughput and scalability of alternate virtual machines like the MoveVM and the SVM to scale Ethereum applications with innovative features like localized fee markets, parallelization, and highly optimized node software.

At launch, the Based Stack will include support for the EVM with OP Stack fraud proofs as we believe that the EVM is, in practice, the most useful for many types of applications. EVM support is especially important for applications that have already deployed on Ethereum and therefore, have written their code bases for the EVM.


---

# 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/execution-environment-virtual-machine.md?ask=<question>&goal=<endgoal>
```

`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.