> For the complete documentation index, see [llms.txt](https://docs.bloxroute.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bloxroute.com/core-solutions/rpc-service/protect-rpc.md).

# Protect RPC

**Protect RPC** routes transactions through bloXroute’s private relay network, keeping them hidden from the public mempool until they are confirmed on-chain. This prevents frontrunning and sandwich attacks by MEV bots, improving execution quality for users.

#### **Key Features**

* **Frontrunning protection** – Transactions are not visible in the public mempool.
* **No setup required** – Works by simply replacing your RPC endpoint in supported wallets like MetaMask.
* **Direct to block proposers** – Transactions are sent privately to validators for inclusion.

#### **How It Works**

When you use Protect RPC, your transaction bypasses the public P2P network and is delivered directly to block proposers via bloXroute’s global Relay network. This ensures:

* No visibility to MEV bots before inclusion
* No sandwiching or frontrunning
* Higher likelihood of receiving the intended execution price

#### **MetaMask Setup**

You can use **Protect RPC** by adding it as a custom network in MetaMask. Here's how:

1. Open **MetaMask** in your browser.
2. Click the **network dropdown** at the top.
3. Select **“Add network”** or **“Add network manually”**.
4. In the form, fill in the fields using the details from the table below.
5. Click **“Save”**.
6. Switch to the new network — transactions will now route through bloXroute’s Protect RPC.

#### **Supported Chains & Endpoints**

<table><thead><tr><th>Network</th><th width="104.4453125">Chain ID</th><th>RPC URL</th></tr></thead><tbody><tr><td>Ethereum</td><td>1</td><td><code>https://eth-protect.rpc.blxrbdn.com</code></td></tr><tr><td>BNB Smart Chain</td><td>56</td><td><code>https://bsc.rpc.blxrbdn.com</code></td></tr></tbody></table>


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.bloxroute.com/core-solutions/rpc-service/protect-rpc.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 `build a script that syncs our docs to a CMS` 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.