> For the complete documentation index, see [llms.txt](https://docs.okkult.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.okkult.io/relay/how-it-works.md).

# How it works

## How it works

The user or app prepares the required transaction data first.

A relayer then broadcasts the final transaction to Ethereum.

### Flow

1. The app generates the required proof locally.
2. The app assembles the target protocol call.
3. A relayer receives the submission request.
4. The relayer sends the transaction on-chain.
5. Ethereum finalizes the result.

### Design notes

* Proof generation remains client-side.
* Relaying is separate from wallet privacy.
* Final state lives on Ethereum Mainnet.

### Next Steps

* Submit a transaction.
* Review **Fee structure**.
* Learn about the **Relayer network**.


---

# 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://docs.okkult.io/relay/how-it-works.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.