Your transactions go straight to 48Club and BlockRazor, who build most BNB Chain blocks, instead of the public mempool, so nobody can trade in front of them while they wait. If neither includes one within two blocks, we broadcast it publicly. See what your swaps gave away →
https://rpc.backrunshield.com
MetaMask may say this URL isn't a known provider yet. That's because we're new: our listing in the public chain list is pending, and the URL is the one shown above.
On a phone, open this page inside your wallet app — Add to wallet works there:
Nothing happens inside Telegram or another app? Open this page in Safari or Chrome first (the ⋯ menu → Open in browser). Or copy the URL above and add it yourself: open BNB Smart Chain in your wallet's network settings, add it as an RPC URL and make it the default.
Works in any wallet, bot or script that takes a custom RPC. Reads are served from our own BSC full node in Tokyo.
Straight to 48Club and BlockRazor, who build most BNB Chain blocks. Your transaction is never gossiped to the public mempool, so nobody can trade in front of it.
Reads come from our own BSC full node in Tokyo, in the same facility as the two builders, not from a resold RPC.
If no builder includes your transaction within two blocks, we broadcast it the ordinary way. Protection never costs you an unmined transaction. The private lane is for people: a wallet sending more than 30 transactions a day is relayed the ordinary way from the 31st.
MetaMask and Rabby send through the network's RPC, which on BNB Chain is usually a public one. Add this endpoint as your BNB Smart Chain network once, and every send goes to the builders privately.
One URL for reads and sends: batched JSON-RPC, filters and receipts, no API key. Point your client at it and nothing else in your code changes.
Use it for eth_sendRawTransaction from your backend, or suggest it to your users. No agreement, no minimum, no exclusivity.
You may not need it. Trust Wallet and Binance Web3 Wallet already send privately on BNB Chain by default, and OKX Wallet has a setting for it (BNB Chain's list). Private sending stops trades placed in front of a pending transaction; it does not stop the backrun after your swap.
Sandwiching requires seeing a transaction while it is still pending. Sent through us, nobody outside the two builders does: it reaches them as a private bundle and is never gossiped to the public mempool. What private routing does not stop is the backrun, an arbitrage placed after your swap has executed, closing the price gap it opened. It cannot change your price, and on BNB Chain today it is mostly done by the builders' own contracts. We may place one backrun of ours directly behind a transaction sent here, in the same private bundle, and 60 % of what it makes after gas is paid to the address that signed the transaction.
A sandwich is the opposite trade: a bot buys in front of you so you pay more, then sells behind you. That needs your transaction to sit in the public mempool long enough to be seen and outbid. Routing privately removes the opportunity rather than competing for it. Measured from our own node over 20 hours in September 2026, sandwiches against users on BNB Chain have become rare — the builders refuse to include them. What still happens to nearly every swap is the backrun behind it; the leak check shows how much that was for your wallet.
A transaction of ours placed in front of yours. Not a probe, not a "protective" order, nothing.
Your transaction leaked, sold, or shown to a third party. It travels to builders as a private bundle.
Custody. You sign, we forward the signed bytes. No account, no deposit, no approval to grant.
Your transaction lands — broadcast publicly by us if no builder takes it within two blocks.
Checkable: every account we trade from is published below, so what we do on chain is open to anyone.
https://rpc.backrunshield.com, chain ID 56, currency BNB.Tested with MetaMask, Rabby, Trust and OKX Wallet. Any wallet that accepts a custom EVM network works — there is nothing bespoke about this endpoint.
Point RPC_URL, BSC_RPC or WEB3_PROVIDER at the endpoint and restart. Batched JSON-RPC arrays and browser CORS both work, so web3.js, ethers, viem and Python's web3 need no changes.
curl -s https://rpc.backrunshield.com \
-H 'content-type: application/json' \
-d '{"jsonrpc":"2.0","id":1,
"method":"eth_chainId","params":[]}'
{"jsonrpc":"2.0","id":1,"result":"0x38"}// ethers v6
const provider = new JsonRpcProvider("https://rpc.backrunshield.com", 56);
const wallet = new Wallet(key, provider); // the key stays in your process
await wallet.sendTransaction(tx); // goes privately to the builders
// viem
const client = createWalletClient({ account, chain: bsc,
transport: http("https://rpc.backrunshield.com") });
# web3.py
w3 = Web3(Web3.HTTPProvider("https://rpc.backrunshield.com"))
w3.eth.send_raw_transaction(signed.raw_transaction)| Method | Behaviour |
|---|---|
| eth_sendRawTransaction | Private to 48Club and BlockRazor for the next block; your hash returns immediately. Broadcast publicly if no builder includes it within 2 blocks. |
| eth_call · eth_estimateGas · eth_getBalance · eth_getCode · eth_getStorageAt · eth_getTransactionCount | Served from our own BSC full node in Tokyo. |
| eth_blockNumber · eth_getBlockByNumber · eth_getBlockByHash · eth_getBlockReceipts · eth_getLogs · eth_getTransactionByHash · eth_getTransactionReceipt | Same node. |
| eth_newFilter · eth_newBlockFilter · eth_getFilterChanges · eth_getFilterLogs · eth_uninstallFilter · eth_getProof · eth_createAccessList | Served too — a dapp that opens a filter works here rather than failing quietly. |
| eth_chainId · net_version · net_peerCount · eth_gasPrice · eth_feeHistory · eth_maxPriorityFeePerGas · eth_blobBaseFee · web3_clientVersion | Answered directly. |
| anything else | Refused with −32601 rather than quietly proxied — admin, debug and trace included. |
120 calls per minute per IP (whole blocks, receipts and log searches count as 10; transactions are never limited) · 128 KB per request body · /health returns the live configuration · /stats the public numbers · /bench the endpoint measurements.
| Node | Our own BSC full node in Tokyo — not a reseller of someone else's RPC. Reads are answered from it directly. |
| Location | Tokyo, in the same facility as the two builders we submit to. Submission acknowledgements measure 2–11 ms. |
| Builders | 48Club and BlockRazor, which together build more than 96 % of BNB Chain blocks. |
| Fallback | Public broadcast after 2 blocks (~0.9 s at BSC's 0.45 s block time) if no builder includes the transaction. |
| Transport | HTTPS with a Let's Encrypt certificate, HTTP redirected, CORS open for browser wallets. |
| Front door | The public endpoint runs on a separate machine; the node itself is never exposed to the internet. |
| Tested | 23 September: a transaction sent through this endpoint was accepted in 23 ms, reached 48Club in 1 ms and BlockRazor in 7 ms, and was mined privately, 0.9 s later — no public broadcast needed. Open it on BscScan. |
We declare this as tracking: limited wherever this endpoint is listed, rather than claiming to store nothing while keeping rows. The rows exist to count what the endpoint handles, for the public numbers on /stats, where anyone can look up one address at a time. The full privacy statement.
https://rpc.backrunshield.com/r/<its address>, receives the 60 % for that flow instead of each user; write to partners@backrunshield.com.Our trading runs from the account below. It calls one contract today, the first one listed; the others are the contracts it called before, each with its dates. That account signs every bundle we place behind other people's trades. A second account sent plain transactions to a second contract on 24–25 September only; that door is closed.
On 5 November we read 440 of our latest transactions back from the chain (the days our node still holds). 323 shared a block with the trade they followed, and every one of those 323 sits at a higher index than it — one slot behind, or a few. The other 117 landed a whole block later, where there is nothing to be in front of. 0 were placed ahead of the trade they backran.
You do not have to take that from us, which is the point of publishing the address. Open it, pick any transaction, and look at what sits immediately above it in the same block: that is the trade we followed. If one of ours is ever found above the trade it was built on, the claim on this page is broken and it will be broken in public.
We are an independent searcher, not a desk. We would rather publish every transaction for anyone to audit than a round number nobody can check.
A bot or front end uses the endpoint the same way a wallet does: send eth_sendRawTransaction to https://rpc.backrunshield.com and your users' transactions reach 48Club and BlockRazor as private bundles, with a public broadcast if neither includes one within two blocks. Reads work too. No key, no account, no exclusivity; switching back is changing the URL.
Revenue share: 60 % of each backrun's realized profit after gas is credited to the sender of the transaction it followed and paid in BNB automatically every hour, as soon as a cent is owed. Flow sent through your own link, https://rpc.backrunshield.com/r/<your address>, pays that 60 % to you instead; write to partners@backrunshield.com.