> For the complete documentation index, see [llms.txt](https://docs.turbine.exchange/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.turbine.exchange/features/private-orderbook.md).
# Private Orderbook
*Pre-settlement privacy*: Your order on Turbine is invisible until it settles.
**Hosted on a TEE**: Turbine runs on a [Trusted Execution Environment](/resources/security/trusted-execution-environment.md) (TEE). No data, including orders, leaves the TEE. The data is completely private. The solver and the price oracle also run on the same TEE.
**Verifiability:** With our attestation service, you can verify that this code runs on the TEE.
{% hint style="info" %}
Turbine's source code is closed during Beta. We will open-source it soon.
{% endhint %}
**Encrypted Transfer**: Your communication with Turbine is encrypted using SSL that terminates only inside the TEE.
No solver, core engineer, market maker, or block builder can see your open order.
#### Further Reading
* [EVIntent - Dark Matter in MEV](https://www.propellerheads.xyz/blog/ev-intent): If open orders are public, you can be frontrun in multi-block frontruns and sandwiches.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.turbine.exchange/features/private-orderbook.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
.gif?alt=media&token=52c94e6f-df7e-4bf4-af1d-ffa412886f60)