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 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
Purchase BSC Private Mempool
Go to the Pricing page to purchase
Apply for Auth
For Details, see Authentication
Subscribe to BSC Private Mempool
For Details, see Request Example
Construct & submit bundle
For Details, see Bundle
Price
The monthly price is $1000; please visit the Pricing page to purchase. Two data streams are allowed per region.
Endpoint
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 tohttps://jp-bscscutum.blockrazor.xyz.Private data streams vary across regions. It is recommended to subscribe to all three endpoints simultaneously.
Tokyo
https://jp-bscscutum.blockrazor.xyz/stream
New York
https://us-bscscutum.blockrazor.xyz/stream
Frankfurt
https://ger-bscscutum.blockrazor.xyz/stream
Dublin
https://ire-bscscutum.blockrazor.xyz/stream
Request Example
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
chainID
string
ETH: 1, BSC:56
hash
string
bundle hash, data streams are pushed uniformly in the form of bundles
nextBlockNumber
uint64
the block number where the bundle is going to be included
maxBlockNumber
uint64
the maximum block number valid for this bundle
proxyBidContract
string
proxy contract address of bundle bidding, biding call for detail can be found in .
refundAddress
string
input parameter of bidding call, the bidding will be refunded to refundAddress in proportion.
refundCfg
int
input parameter of bidding call
txs
hash
string
transaction hash
from
string
sender of the transaction
to
string
receiver of the transaction
value
hex
value being transacted
nonce
uint64
nonce
calldata
string
calldata
functionSelector
string
the first 4 bytes of the contract function signature hash
log
address
string
the smart contract address that triggered the event
topics
[]string
event log topcis
data
string
storage area for non-index data
state
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
"0x7C3b……3cb9E2"
[]string
The address of the state object where the data changes, which can be EOA or smart contract
"0x935b……6cf608"
string
the Key of the changed data in state object
"0x0000……3ffc00"
string
the Value of changed data in state object
Data Stream Example(default)
Data Stream Example(including state)
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
Last updated
Was this helpful?