# Open Execution Network

Liberty DEX relies on an open network of independent third-party executors to fulfill swap orders.

These participants compete to execute user intents by sourcing liquidity from multiple on-chain venues, internal inventory, or advanced routing strategies. Because execution is competitive, participants are incentivized to deliver the most efficient trade in order to capture the order.

This architecture can improve swap outcomes for users in several ways:

#### Price improvement through aggregated liquidity

Executors are able to route trades across multiple liquidity sources rather than relying on a single pool. By combining liquidity from different venues, Liberty DEX can often deliver better execution prices than a direct AMM swap.

#### Gasless swap submission

Orders are signed off-chain and executed by network participants. The executor who fulfills the order is responsible for submitting the transaction, removing the need for users to pay network fees directly.

#### No cost for failed execution

If an order cannot be completed, no on-chain transaction is submitted by the user. As a result, users avoid the network costs typically associated with failed transactions.

#### Reduced exposure to MEV

Executors may submit transactions through private relays or protected execution channels, reducing the likelihood of front-running and other MEV extraction strategies that can negatively impact swap outcomes.

<br>


---

# Agent Instructions: 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.libertyswap.finance/liberty-dex/execution-model/open-execution-network.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.