> For the complete documentation index, see [llms.txt](https://gasyard-1.gitbook.io/gasyard/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gasyard-1.gitbook.io/gasyard/technical-implementaion/mev-protection.md).

# MEV Protection

#### **How Gasyard Protects Against MEV**

1. **Private RPC Transactions**

* Wherever necessary, transactions are sent through private RPC endpoints, preventing them from being publicly visible before execution. This reduces the risk of front-running or sandwich attacks.

2. **No Swaps, No Slippage Risks**

* Unlike traditional bridges that rely on AMMs for swapping assets, Gasyard operates purely as a cross-chain settlement layer. Solvers fulfill user requests directly, ensuring that users receive the exact amount specified without exposure to slippage.

3. **Solver-Based Execution**

* Transactions are executed by solvers who commit to fulfilling user intents based on predefined parameters. Since solvers handle liquidity provisioning and transaction finalization, MEV strategies like back-running have no impact on the user experience.

By designing Gasyard with intent-based execution and solver-driven fulfillment, we minimize MEV risks while ensuring fast and reliable cross-chain transfers.


---

# 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://gasyard-1.gitbook.io/gasyard/technical-implementaion/mev-protection.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.