> 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/streams/mempool/bsc/private-mempool.md).

# Private Mempool

### What is BSC Private Mempool

BSC Private Mempool is a private pending transaction service provided by BlockRazor, used to obtain private orderflow from BlockRazor RPC.

Unlike Public Mempool, which subscribes to pending transactions in public distribution, Private Mempool focuses on private transaction data that hasn't entered the public distribution path. This data is pushed via the SSE protocol, allowing users to directly parse, filter, and process it within their strategy systems. Private Mempool performs uniform anonymization on transaction content, disclosing only the transaction fields authorized for public access. This balances data privacy with the retention of critical information needed for strategy analysis.

### Scenarios of BSC Private Mempool

Private Mempool is suitable for users who want to monitor, judge, and execute strategies around private orderflows. Common scenarios include backrunning, copy trading, and sniping.

* **Backrunning**: When a trade appears in the private orderflow that may trigger arbitrage opportunities, users can construct a backrun trade based on these signals and execute the strategy after the target trade.
* **Copy Trading**: When target addresses, strategy accounts, or specific types of transactions appear in the private orderflow, users can identify these copy trading signals earlier and build follow strategies around actions such as buying, selling, adding to positions, or adjusting positions.
* Sniping: Identify key signals from private orderflow as early as possible when new pools are created, liquidity is injected, tokens open, or specific target trades are about to trigger market changes, providing an earlier response window for quick entry, signal following, and other timing-sensitive strategies.

### Why choose BSC Private Mempool?

In the BSC scenario, many high-value transactions do not appear in the public Mempool, but are instead included via a private routing provided by BlockRazor RPC. For users who want to build strategies around these transactions, waiting until the transactions are finally included to capture signals often means missing more valuable processing opportunities.

Private Mempool relies on [BEF](/core-technology/blockchain-edge-fabric.md) to provide users in different regions with access to private orderflow, enabling users to conduct earlier analysis and decisions based on the private transactions.

### Quick Start

{% stepper %}
{% step %}
**Purchase BSC Private Mempool**

Go to the [Pricing](https://blockrazor.io/#/pricing) page to purchase
{% endstep %}

{% step %}
**Apply for Auth**

For Details, see [Authentication](/get-started/authentication.md)
{% endstep %}

{% step %}
**Subscribe to BSC Private Mempool**

For Details, see [Request Example](#request-example)
{% endstep %}

{% step %}
**Construct &  submit bundle**

For Details, see [Bundle](/transaction-submission/rpc/bsc/eth_sendmevbundle/searcher.md)
{% endstep %}
{% endstepper %}

### Price

The monthly price is $1000; ​​please visit the [Pricing](https://blockrazor.io/#/pricing) page to purchase. Two data streams are allowed per region.

### Endpoint

{% hint style="info" %}

* Please keep the domain for subscribing to bundles consistent with the domain for sending bundles. For example, if you subscribe to `https://jp-bscscutum.blockrazor.xyz/stream`, send bundles to `https://jp-bscscutum.blockrazor.xyz`.
* Private data streams vary across regions. It is recommended to subscribe to all three endpoints simultaneously.
  {% endhint %}

<table><thead><tr><th width="129.359375">地區</th><th>端點</th></tr></thead><tbody><tr><td>Tokyo</td><td>https://jp-bscscutum.blockrazor.xyz/stream</td></tr><tr><td>New York</td><td>https://us-bscscutum.blockrazor.xyz/stream</td></tr><tr><td>Frankfurt</td><td>https://ger-bscscutum.blockrazor.xyz/stream</td></tr><tr><td>Dublin</td><td>https://ire-bscscutum.blockrazor.xyz/stream</td></tr></tbody></table>

### Request Example

```json
curl -X GET \
    -H "Content-Type: application/json" \
    -H "Authorization: Bearer <token>" \
    --data '{}' \
    https://jp-bscscutum.blockrazor.xyz/stream
```

```
https://jp-bscscutum.blockrazor.xyz/stream?token=<token>
```

### Data Stream Type

#### **Raw Bundle**

Raw Bundle refers to the bundle that has not been followed by the strategy transaction. Transactions in Raw Bundle come from two channels.

Transactions submitted through `eth_sendRawTransaction` will be automatically constructed as a bundle by BlockRazor RPC and pushed to Private Mempool. The Raw Bundle in this scenario only contains one transaction;

For the Raw Bundle submitted through `eth_sendMevBundle`, the transactions come from the public mempool or are self-constructed. The Raw Bundle in this scenario can contain up to 50 transactions.

#### Followed Bundle

After the client executes the backrun, coping trading or sniping strategy on Raw Bundle, it can choose to continue to disclose the bundle to Private Mempool to execute the nested backrun strategy. At this time, the bundle disclosed to the Private Mempool is the Followed Bundle, which contains all transactions in Raw Bundle, and one strategy transaction.

### Data Stream Structure

**Bundle**

<table><thead><tr><th width="169">Patameters</th><th width="131">Format</th><th>Remark</th></tr></thead><tbody><tr><td>chainID</td><td>string</td><td>ETH: 1, BSC:56</td></tr><tr><td>hash</td><td>string</td><td>bundle hash, data streams are pushed uniformly in the form of bundles</td></tr><tr><td><a href="#tx">txs</a></td><td><a href="#tx">[]tx</a></td><td>transactions included in bundle</td></tr><tr><td>nextBlockNumber</td><td>uint64</td><td>the block number where the bundle is going to be included</td></tr><tr><td>maxBlockNumber</td><td>uint64</td><td>the maximum block number valid for this bundle</td></tr><tr><td>proxyBidContract</td><td>string</td><td>proxy contract address of bundle bidding,  biding call for detail can be found in <a data-mention href="/pages/ugvQCt84QW0SIkVonADF">/pages/ugvQCt84QW0SIkVonADF</a>.</td></tr><tr><td>refundAddress</td><td>string</td><td>input parameter of bidding call, the bidding will be refunded to refundAddress in proportion.</td></tr><tr><td>refundCfg</td><td>int</td><td>input parameter of bidding call</td></tr><tr><td>state</td><td>[]state</td><td>state change of state objects in EVM,   <a href="#data-stream-example-including-state">data stream example</a></td></tr></tbody></table>

**txs**

<table><thead><tr><th width="195">Patameters</th><th width="132">Format</th><th>Remark</th></tr></thead><tbody><tr><td>hash</td><td>string</td><td>transaction hash</td></tr><tr><td>from</td><td>string</td><td>sender of the transaction</td></tr><tr><td>to</td><td>string</td><td>receiver of the transaction</td></tr><tr><td>value</td><td>hex</td><td>value being transacted</td></tr><tr><td>nonce</td><td>uint64</td><td>nonce</td></tr><tr><td>calldata</td><td>string</td><td>calldata</td></tr><tr><td>functionSelector</td><td>string</td><td>the first 4 bytes of the contract function signature hash</td></tr><tr><td>logs</td><td><a href="#log">[]log</a></td><td>event logs emitted during transaction execution</td></tr></tbody></table>

**log**

<table><thead><tr><th width="199">Patameters</th><th width="132">Format</th><th>Remark</th></tr></thead><tbody><tr><td>address</td><td>string</td><td>the smart contract address that triggered the event</td></tr><tr><td>topics</td><td>[]string</td><td>event log topcis</td></tr><tr><td>data</td><td>string</td><td>storage area for non-index data</td></tr></tbody></table>

#### **state**

{% hint style="info" %}
the default data stream does not contain `state` field, if you need it, please modify the url of RPC Endpoint to <https://jp-bscscutum.blockrazor.xyz/stream?state=true>
{% endhint %}

<table><thead><tr><th width="208">Patameters</th><th width="123">Format</th><th>Remark</th></tr></thead><tbody><tr><td>"0x7C3b……3cb9E2"</td><td>[]string</td><td>The address of the state object where the data changes, which can be EOA or smart contract</td></tr><tr><td>"0x935b……6cf608"</td><td>string</td><td>the Key of the changed data in state object</td></tr><tr><td>"0x0000……3ffc00"</td><td>string</td><td>the Value of changed data in state object</td></tr></tbody></table>

### Data Stream Example(default)

```json
{
    "chainID":"56" //ETH: 1, BSC:56
    "hash":"0x2ba4c05436d4a48a0ce30341a3164b34b31c091a28ed62618f7b0512aba41f51" // bundle hash
    "txs":[{
          "hash":"0x2ba4c05436d4a48a0ce30341a3164b34b31c091a28ed62618f7b0512aba41f51"
          "from":"0xB4647b856CB9C3856d559C885Bed8B43e0846a47"
          "to":"0x0000000000000000000000000000000000001000"
          "value":"0x1c4eda9192000"
          "nonce":88036
          "calldata":"0xf340fa01000000000000000000000000b4647b856cb9c3856d559c885bed8b43e0846a47"
          "functionSelector":"0xe47d166c"
          "logs":[
              {
                "address": "0x6c1bcf1b99d9f0819459dad661795802d232437e",
                "topics": ["0xc42079f94a6350d7e6235f29174924f928cc2ac818eb64fed8004e115fbcca67", "0x0000000000000000000000000000000000000000000000000000000000000000", "0x0000000000000000000000000000000000000000000000000000000000000000"],
                "data": "0x"
              }
              {
                "address": "0x6c1bcf1b99d9f0819459dad661795802d232437e",
                "topics": ["0xc42079f94a6350d7e6235f29174924f928cc2ac818eb64fed8004e115fbcca67", "0x0000000000000000000000000000000000000000000000000000000000000000", "0x0000000000000000000000000000000000000000000000000000000000000000"],
                "data": "0x"
              }
          ]
    }]
    "nextBlockNumber":39177941  //the block number where the bundle is going to be included
    "maxBlockNumber":39177941  //the maximum block number valid for this bundle
    "proxyBidContract":"0x74Ce839c6aDff544139f27C1257D34944B794605" //bidding contract address, call the contract's proxyBid method to bid
    "refundAddress":"0x6c1bcf1b99d9f0819459dad661795802d232437e", //the bidding amount will be refunded to refundAddress in proportion
    "refundCfg":10380050 //refund configuration
}
```

### Data Stream Example(including state)

{% hint style="info" %}
The default data stream does not contain `state` field, if you need to obtain it, please modify the url of RPC Endpoint to <https://bsc.blockrazor.xyz/stream?state=true>
{% endhint %}

```json
{
    "chainID":"56" //ETH: 1, BSC:56
    "hash":"0x2ba4c05436d4a48a0ce30341a3164b34b31c091a28ed62618f7b0512aba41f51" // bundle hash
    "txs":[{
          "hash":"0x2ba4c05436d4a48a0ce30341a3164b34b31c091a28ed62618f7b0512aba41f51"
          "from":"0xB4647b856CB9C3856d559C885Bed8B43e0846a47"
          "to":"0x0000000000000000000000000000000000001000"
          "value":"0x1c4eda9192000"
          "nonce":88036
          "calldata":"0xf340fa01000000000000000000000000b4647b856cb9c3856d559c885bed8b43e0846a47"
          "functionSelector":"0xe47d166c"
          "logs":[
              {
                "address": "0x6c1bcf1b99d9f0819459dad661795802d232437e",
                "topics": ["0xc42079f94a6350d7e6235f29174924f928cc2ac818eb64fed8004e115fbcca67", "0x0000000000000000000000000000000000000000000000000000000000000000", "0x0000000000000000000000000000000000000000000000000000000000000000"],
                "data": "0x"
              }
              {
                "address": "0x6c1bcf1b99d9f0819459dad661795802d232437e",
                "topics": ["0xc42079f94a6350d7e6235f29174924f928cc2ac818eb64fed8004e115fbcca67", "0x0000000000000000000000000000000000000000000000000000000000000000", "0x0000000000000000000000000000000000000000000000000000000000000000"],
                "data": "0x"
              }
          ]
    }]
    "nextBlockNumber":39177841  //the block number where the bundle is going to be included
    "maxBlockNumber":39177941  //the maximum block number valid for this bundle
    "proxyBidContract":"0x74Ce839c6aDff544139f27C1257D34944B794605" //bidding contract address, call the contract's proxyBid method to bid
    "refundAddress":"0x6c1bcf1b99d9f0819459dad661795802d232437e", //the bidding amount will be refunded to refundAddress in proportion
    "refundCfg":10380050 //refund configuration
    "state": { //state change of state objects
	"0x7C3b00CB3B40Cc77d88329A58574E29cFA3cb9E2": { //The address of the state object where the data changes, which can be EOA or smart contract
	      "0x935b605129a438014d6ae0692623c5e1fbf83d5a631f5a0f8489a301966cf608": "0x00000000000000000000000000000000000000000000010c86a7e418723ffc00"
	      //"the Key of the changed data in state object":"the Value of changed data in state object"
	      }
      }
}
```


---

# 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/streams/mempool/bsc/private-mempool.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.