> For the complete documentation index, see [llms.txt](https://docs.wheelx.fi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wheelx.fi/overview/features/smart-contracts/architecture.md).

# Architecture

WheelX separates off-chain route discovery and transaction preparation from user-authorized on-chain execution. Users retain custody of their assets and approve or sign transactions through their own wallets.

<figure><img src="/files/nkXzvHzOOpG1qWOcqN1H" alt=""><figcaption></figcaption></figure>

This diagram is a conceptual overview of the EVM execution flow. Individual routes may use different external protocols and execution steps.

### Execution Flow

1. **Quote and route preparation**: WheelX's API or SDK evaluates available routes and prepares the transaction data required for execution.
2. **User authorization**: The transaction is returned to the user's wallet for approval and signature.
3. **On-chain execution**: Published WheelX EVM components support token approvals, DEX routing, and native-asset receiving flows.
4. **External protocol execution**: DEX liquidity and cross-chain transfers are executed through integrated external protocols according to the selected route.

### Published EVM Components

* **ERC20 Approval Proxy**: Supports ERC20 token approval within applicable execution flows.
* **Dex Router**: Executes authorized on-chain routing and DEX interactions.
* **WheelX Native Token Receiver**: Receives native assets within supported transaction flows.
* **Maker and Dispatcher**: Published EOA addresses used by the WheelX execution system.

Contract and EOA addresses are listed on the [Deployment Addresses](/overview/features/smart-contracts/deployment-addresses.md) page.

### Security Model

* Users retain custody and authorize transactions from their own wallets.
* Contract and execution addresses are published for independent verification.
* Execution is separated from off-chain quote and route preparation.
* Available security reviews are published under [Contract Audit Reports](/overview/safety-and-security/contract-audits-reports.md).

>


---

# 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://docs.wheelx.fi/overview/features/smart-contracts/architecture.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.