Backrun Shield

Private transaction routing for BNB Smart Chain.

Your transactions go straight to the block builders instead of the public mempool — nobody can sandwich what nobody can see. We backrun behind you, never in front, and pay back most of what that earns.

Endpointchecking…
Chain
Block height
Your round trip
Queried from your browser, refreshed every 10 seconds.

BSC · MEV-protected RPC

Chain ID 56
https://rpc.backrunshield.com

No key, no signup, no account. Works in any wallet or bot that takes a custom RPC.

What you get

Private routing

Straight to 48Club and BlockRazor, who build most BNB Chain blocks. Your transaction is never gossiped to the public mempool, so a sandwich bot never sees it in time.

Backrun rebate

We trade behind you to restore the price your swap moved, and split what that earns — 50 % from the first day, up to 80 % at volume, in BNB.

No dead ends

If no builder includes your transaction within two blocks, we broadcast it the ordinary way. Protection never costs you an unmined transaction.

The path a transaction takes
your wallet Backrun Shield 48Club BlockRazor block your tx, then ours not included in 2 blocks → we broadcast it publicly

Sandwiching requires seeing a transaction while it is still pending. Here nobody does. What we do instead is backrun: our own trade executes after yours, closing the price gap your swap opened. It cannot affect your price — your swap has already executed when ours runs — which is why protecting you and earning from your flow are the same job rather than opposing ones.

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.

The rules we operate under
Never

A transaction of ours placed in front of yours. Not a probe, not a "protective" order, nothing.

Never

Your transaction leaked, sold, or shown to a third party. It travels to builders as a private bundle.

Never

Custody. You sign, we forward the signed bytes. No account, no deposit, no approval to grant.

Always

Your transaction lands — broadcast publicly by us if no builder takes it within two blocks.

Always

On chain and checkable: every backrun is a transaction you can read, every rebate a transfer you can watch.

Connect

Any wallet

  1. Press Add to wallet above, or add a custom network manually.
  2. RPC URL https://rpc.backrunshield.com, chain ID 56, currency BNB.
  3. Select it. Same chain, same balances, same contracts.

Tested with MetaMask, Rabby, Trust and OKX Wallet. Any wallet that accepts a custom EVM network works — there is nothing bespoke about this endpoint.

Any bot or script

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"}

What the endpoint serves

MethodBehaviour
eth_sendRawTransactionPrivate 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_getTransactionCountServed from our own BSC full node in Tokyo.
eth_blockNumber · eth_getBlockByNumber · eth_getBlockByHash · eth_getBlockReceipts · eth_getLogs · eth_getTransactionByHash · eth_getTransactionReceiptSame node.
eth_newFilter · eth_newBlockFilter · eth_getFilterChanges · eth_getFilterLogs · eth_uninstallFilter · eth_getProof · eth_createAccessListServed 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_clientVersionAnswered directly.
anything elseRefused with −32601 rather than quietly proxied — admin, debug and trace included.

600 requests per minute per IP · 128 KB per request body · /health returns the live configuration · /stats the public numbers · /bench the endpoint measurements.

Infrastructure
NodeOur own BSC full node in Tokyo — not a reseller of someone else's RPC. Reads are answered from it directly.
LocationTokyo, in the same facility as the two builders we submit to. Submission acknowledgements measure 2–11 ms.
Builders48Club and BlockRazor, which together build more than 96 % of BNB Chain blocks.
FallbackPublic broadcast after 2 blocks (~0.9 s at BSC's 0.45 s block time) if no builder includes the transaction.
TransportHTTPS with a Let's Encrypt certificate, HTTP redirected, CORS open for browser wallets.
Front doorThe public endpoint runs on a separate machine; the node itself is never exposed to the internet.
How the rebate is computed

For each transaction you send us, we record its hash and your address. If one of our trips lands behind it in the same block, we read what that trip realized from the receipt's own logs — the tokens our contract actually received, minus the gas it burned — and your share is a percentage of that figure.

your share = (tokens our trip received − gas it paid) × 50 %

# 80 % above volume. Paid in BNB, daily, from a named address.
# Every line names your transaction hash, ours, and the amount.

Nothing is estimated and nothing is averaged: if a backrun did not land, it earned nothing and is not counted. Transactions we cannot backrun are still routed privately at no cost to you — the protection is not conditional on us making money.

What we keep, and for how long

Stored

  • The signed transaction bytes and its hash
  • The sending address, so a rebate can be paid
  • Timestamp, and the requesting IP for rate limiting

Not stored, not possible

  • Private keys — your wallet signs locally, we receive finished bytes
  • Any ability to alter, replace or delay a transaction beyond forwarding it
  • Sales or sharing of your flow with third parties

We declare this as tracking: limited wherever this endpoint is listed, rather than claiming to store nothing while keeping rows. The rows exist for one reason: to build the backrun and to know who to pay.

Questions people ask first
How do you make money if this is free?
By backrunning — trading behind your transaction to close the price gap it opens. That is a normal, public activity on every chain; the difference here is that we share it with you instead of keeping all of it, and we never take the other side that would cost you money.
Can you see or move my funds?
No. Your wallet signs locally and sends us the finished bytes. We cannot alter, replace or spend anything — only forward it or, in the worst case, fail to forward it, in which case we broadcast it publicly.
Is it slower than a public RPC?
Sending is not: the transaction reaches a builder in milliseconds. Inclusion depends on a builder taking it, and if none does within two blocks we broadcast publicly — so the worst case is roughly a second later than the public mempool, and the normal case is the same block.
What happens if your endpoint goes down?
Your wallet errors like any RPC outage and you switch networks. Nothing is stuck on our side: a transaction we have already accepted is broadcast publicly within two blocks if no builder takes it.
Do I need to trust you not to front-run me?
Less than it sounds. Our trips are on chain; anyone can read the blocks and see our transactions sitting behind the triggers, never ahead of them. The moment that stopped being true, it would be public within a day.
Does this work for contract deployments and approvals?
Yes — any signed transaction is routed the same way, whether it is a swap, an approval, a transfer or a deployment. Only swaps tend to create a backrun, so only they tend to earn a rebate.
Who runs this?
An independent searcher on BNB Smart Chain, with its own full node and executor contract in Tokyo — in the same facility as the builders we submit to. Not affiliated with BNB Chain, PancakeSwap, 48Club or BlockRazor.
For bots, aggregators and desks

Send us your users' flow, keep most of what it earns.

Two builders produce more than 96 % of BNB Chain blocks, and they run their own arbitrage inside the blocks they build. In one 24-hour measurement of gaps we could have taken, 891 went to builder-owned contracts and 1,016 to private 0.05-gwei bundles before anyone else had a chance. That value comes out of your users' trades, and today none of it returns to you.

Route your users here and we split what their flow earns — 50 % from the first day, up to 80 % above volume — paid in BNB, daily, from an address you can watch. No exclusivity, no minimum, cancel whenever.

Before either side commits: send your router address and we will measure what its flow was worth over a day, from our own node, and show you the working.

Your own endpoint URL, right now

Put your BNB address in and point your users, bot or front end at the link it makes. It is this same endpoint — every transaction that arrives through it is recorded against your address, and paid from what that flow earns. Nothing to sign up for, and you can check the total any day on the stats page.

https://rpc.backrunshield.com/r/0x…