> For the complete documentation index, see [llms.txt](https://txswap.gitbook.io/tx-swap/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://txswap.gitbook.io/tx-swap/more-about-tx/solvers/introduction.md).

# Introduction

### Intent-based Trading 

TX Swap employs an intent-based trading model that sets it apart from other DEXs. On TX Swap, users are not responsible for executing their trades directly. Instead of creating an Ethereum transaction for swapping tokens, incurring gas costs and potential failures, users sign an intent specifying the desired tokens and a limit price.

Once the user signs the intent, it is passed on to solvers, who are third-party participants. These solvers compete for the user's order flow, aiming to offer the most favorable execution price. The solver that provides the best price is granted the authority to settle the user's order. Subsequently, the solver generates and signs the actual settlement transaction.

### Solvers

In the TX Swap ecosystem, solvers can move tokens on behalf of the user. They utilize the ERC20 approvals granted by the user to the settlement contract. Throughout this process, the contract verifies the user's intent signature and ensures that the execution adheres to the specified limit price and quantity.

In the following sections, we delve into a more detailed explanation of how the competition operates presently. We provide a concrete guide on how to become a solver on TX Swap and also share our vision for the future of fully decentralizing this competitive framework.

TX Swap embraces the intent-based trading model, allowing users to delegate the trade execution process to solvers. Solvers compete to offer the best prices, ensuring efficient and reliable trade settlements for users on the platform.


---

# 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://txswap.gitbook.io/tx-swap/more-about-tx/solvers/introduction.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.