> For the complete documentation index, see [llms.txt](https://docs.blockrazor.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.blockrazor.io/transaction-submission/rpc/overview.md).

# Overview

### What is BlockRazor RPC?

BlockRazor RPC is a transaction submission channel for Ethereum, BSC, and Base, providing users with transaction privacy protection, MEV protection, and real-time refund.

In public RPC, user-submitted transactions typically enter the public propagation path and are broadcast in the node network, making it easier to expose the transaction intent and make the transaction susceptible to malicious MEV attacks such as sandwiching and frontrunning. This may not only result in a worse transaction price, but may also cause the potential value that originally belonged to the user to be stolen by external strategies.

In contrast, BlockRazor RPC keeps transactions within a private chain, reducing the risk of malicious exploitation during public dissemination. Furthermore, BlockRazor RPC allows for customized configuration of the scope of transaction data disclosure, providing only publicly available information to the Searcher for harmless backrun strategies while ensuring transaction security, and returning a portion of the resulting revenue to the user in real time.

### What does BlockRazor RPC offer?

BlockRazor RPC primarily provides the following capabilities:

* Protecting transaction privacy and reducing the risks associated with public dissemination.
* Defend against malicious MEV attacks such as sandwich and frontrunning
* Support harmless backrun through a controlled data disclosure mechanism
* A portion of the backrun revenue will be returned to users in real time.
* It supports quick integration by project teams and allows customization of RPC domains and related configurations.

### Who is BlockRazor RPC suitable for?

* **Wallets / DEXs**: Team aiming to improve transaction protection, optimize the user trading experience, and introduce a rebate mechanism.
* **Trading Bot / Quant Team**: Team aiming to reduce malicious MEV interference when submitting trades, while also ensuring execution quality.
* **Project Builders**: Projects requiring dedicated RPC integration and desiring customized transaction disclosure and refund configurations.
* Trading users: Users who want a more secure trading path on Ethereum and BSC.

### Why choose BlockRazor RPC?

**High security**: BlockRazor RPC provides MEV protection for all types of transactions on Ethereum and BSC, focusing on defending against highly dangerous attack such as sandwich and frontrunning. It also employs a high-threshold access policy for the Seacher, combined with real-time MEV attack monitoring, further reducing user transaction risks.

**Fast Inclusion**: BlockRazor RPC, based on [BEF](/core-technology/blockchain-edge-fabric.md), sends transactions to block-producing nodes with the lowest latency and highest value to achieve better inclusion performance.

Real-time refunds: When a user's transaction has an executable and harmless backrun space, Searcher can construct a backrun strategy based on the authorized disclosed transaction information and return a portion of the profits to the user in real time.

**Lightning-fast integration**: BlockRazor RPC maintains the standard JSON-RPC usage, facilitating rapid integration by wallets, DEXs, trading bots, and projects. For ordinary users, it can be used directly like standard RPC; for projects, BlockRazor RPC also supports configurations such as custom domains, transaction disclosure policies, refund addresses, and revert protection, enabling integration and deployment at a lower cost.

### FAQ

<details>

<summary>Why can you earn refunds while your transaction is protected by MEV?</summary>

Because BlockRazor RPC supports disclosing transaction information according to custom rules, searchers can execute harmless backrun strategies based on this authorized disclosure data, rather than harmful sandwich or frontrunning attacks. A portion of the revenue generated by the backrun is returned to the user in real time.

</details>

<details>

<summary>When will the rebate arrive in my account? In what form will it be processed?</summary>

If a user transaction has executable backrun space, Searchers will process the refund in real time on-chain. Typically, the refund transaction will be executed within the same block as the user transaction.

</details>

<details>

<summary>Will the transaction revert?</summary>

If BlockRazor RPC detects that a transaction will be reverted and the channel to which the transaction belongs has revert protection enabled, then the transaction will not be included in the blockchain.

</details>

<details>

<summary>How are the profits distributed?</summary>

Once a transaction is profitable and successfully included, a portion of the revenue will be returned to the user, while the remainder will be used to pay for BlockRazor RPC's service fees and the costs incurred by the builder in securing a better inclusion position.

</details>

### Privacy Statement

BlockRazor RPC does not track any type of user information (such as IP address, location, etc.). It only retains information publicly available on the blockchain, such as transaction timestamps.


---

# 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.blockrazor.io/transaction-submission/rpc/overview.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.