> For the complete documentation index, see [llms.txt](https://docs.grix.finance/grix/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.grix.finance/grix/grix-protocol/execution-layer.md).

# Execution Layer

The execution layer is responsible for the fulfillment of the order and ensuring its successful finalization. Once an order’s solution batch has been prioritized by Socrates, the transaction builder takes over to facilitate the actual transaction data code using an [<mark style="color:purple;">open-source transaction building library</mark>](https://github.com/grixprotocol) (managed by Grix). It then ships the built transaction to an automated execution network (such as Gelato) to be executed.

Finally, the transaction is transmitted to the blockchain through the Grix router contract. The router also deducts fees and channels them to the fees pool, which then distributes these fees between the protocol and the solvers.

The execution layer also manages the intricacies of transaction execution and ensures that each trade is processed fast, securely, efficiently, and in compliance with the priorities and protocol fees agreed by the user.

Simplified overview of the Execution Layer:

<figure><img src="https://content.gitbook.com/content/n3odl4ymHi6P7lINhkcx/blobs/r9zvVNqOWjHV4t1YG733/Execution%20Layer.png" alt=""><figcaption><p>The Execution Layer</p></figcaption></figure>


---

# 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.grix.finance/grix/grix-protocol/execution-layer.md?ask=<question>&goal=<user_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.