> 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/bsc/bsc-rpc-endpoint.md).

# BSC RPC Endpoint

### General Endpoints

<table data-search="false"><thead><tr><th width="127.3359375"></th><th width="186">default</th><th width="196">fullprivacy</th><th>maxbackrun</th></tr></thead><tbody><tr><td>URL</td><td>https://bsc.blockrazor.xyz</td><td>https://bsc.blockrazor.xyz/fullprivacy</td><td>https://bsc.blockrazor.xyz/maxbackrun</td></tr><tr><td>MEV Protection</td><td>Enabled</td><td>Enabled</td><td>Enabled</td></tr><tr><td>Transaction Privacy</td><td>Minimal disclosure</td><td>Full privacy</td><td>Maximum disclosure</td></tr><tr><td>Rebate Potential</td><td>Medium</td><td>No rebate</td><td>High</td></tr><tr><td>Rebate Percentage</td><td>Supported</td><td>No rebate</td><td>Supported</td></tr><tr><td>Revert Protection</td><td>Disabled</td><td>Enabled</td><td>Enabled</td></tr></tbody></table>

<details>

<summary><strong>default Mode</strong></summary>

In `default` mode, transactions submitted through BSC RPC disclose only the necessary transaction data to Searchers (`hash`, `logs`, and state changes). This provides opportunities for rebates while protecting transaction privacy as much as possible. To prioritize fast block inclusion, revert protection is not enabled in this mode.

</details>

<details>

<summary><strong>fullprivacy Mode</strong></summary>

In `fullprivacy` mode, transactions submitted through BSC RPC do not disclose any transaction data. BSC RPC forwards the transactions directly to mainstream Builders. Because no transaction data is disclosed, transactions in this mode do not generate rebates, and no rebate percentage needs to be configured. Revert protection is enabled in this mode.

</details>

<details>

<summary><strong>maxbackrun Mode</strong></summary>

In `maxbackrun` mode, transactions submitted through BSC RPC disclose the transaction data required to maximize rebate opportunities while maintaining privacy protection. The disclosed fields include `hash`, `to`, `calldata`, `functionSelector`, `logs`, and state changes. Revert protection is enabled in this mode.

</details>

### Dedicated Endpoints

A dedicated endpoint is a private transaction channel provided by BlockRazor for an individual user or project. Users can configure dedicated endpoints in the BlockRazor console, including customizing the endpoint URL for easier identification and configuring transaction disclosure parameters and rebate recipient addresses.

After adding a dedicated endpoint to a wallet or integrating it into a project, users can view its transactions and rebate records in the BlockRazor console.

<table><thead><tr><th width="148.8359375">Endpoint</th><th width="551.25390625">Example URL</th></tr></thead><tbody><tr><td>Dedicated Endpoint URL</td><td>https://bsc.blockrazor.xyz/&#x3C;rpc_id></td></tr><tr><td>Custom Endpoint URL</td><td>https://&#x3C;custom_content>.bsc.blockrazor.xyz</td></tr></tbody></table>

### Regional Endpoints

<table><thead><tr><th width="148.99609375">Region</th><th>Endpoint</th></tr></thead><tbody><tr><td>Tokyo</td><td>https://jp-bscscutum.blockrazor.xyz</td></tr><tr><td>New York</td><td>https://us-bscscutum.blockrazor.xyz</td></tr><tr><td>Frankfurt</td><td>https://ger-bscscutum.blockrazor.xyz</td></tr><tr><td>Dublin</td><td>https://ire-bscscutum.blockrazor.xyz</td></tr></tbody></table>

Regional endpoints are suitable for projects that are highly sensitive to transaction latency and whose transaction sources are concentrated in specific regions.


---

# 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/bsc/bsc-rpc-endpoint.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.