# Backrun Shield

> An MEV-protected JSON-RPC endpoint for BNB Smart Chain (chain ID 56), run by the searcher itself rather than resold
> from another provider. Transactions are routed privately to the block builders instead of the public mempool, and half
> of what backrunning them earns is paid back to the sending address.

Endpoint: https://rpc.backrunshield.com
Chain: BNB Smart Chain, chain ID 56 (0x38)
Account, API key, signup: none
Rate limit: 600 requests per minute per IP

## What it does

- eth_sendRawTransaction is submitted privately to 48Club and BlockRazor, who build the large majority of BNB Chain
  blocks. The transaction is never gossiped to the public mempool, so nobody can trade in front of it.
- If no builder includes it within 2 blocks (~0.9 s), it is broadcast publicly, so protection never costs an unmined
  transaction.
- Reads are served from the operator's own BSC full node in Tokyo: the standard eth_*, net_* and web3_* methods,
  including eth_getBlockReceipts, eth_getProof, eth_createAccessList and the filter methods. debug_*, trace_* and
  admin_* are refused, and nothing that signs is served.
- A backrun that lands behind a user's transaction pays that user 50 % of what it realized, in BNB, rising to 80 % at
  volume. The realized figure is read from the receipt's own logs.

## What BNB Chain swaps leak (measured)

- Every swap moves a pool's price; an arbitrage placed right behind it in the same block takes the difference. The
  operator measures this live from its own node and publishes it at https://backrunshield.com/leaks, with a lookup for
  any wallet and every backrun linked on BscScan.
- First reading, 23 September 2026 (about 20 minutes, 3,318 swaps from 973 wallets): about $2,300 taken, 97 % of it by
  the block builders' own arbitrage contracts (48Club and BlockRazor) inside their own blocks.
- Sandwich attacks against users were measured too: over ~20 hours of blocks, essentially none. On BNB Chain today the
  value leaks to backruns, not sandwiches.

## Honest limits

- Latency for reads is ordinary; the point is where sends go, not how fast quotes come back.
- The operator keeps the submitted transaction bytes, sending address, timestamp and requesting IP — declared as
  "tracking: limited", not "none".
- Not affiliated with BNB Chain, PancakeSwap, 48Club or BlockRazor.

## Pages

- https://backrunshield.com/ — what it is, how to point a wallet or a bot at it, the method table, the FAQ
- https://backrunshield.com/leaks — what swaps leak to the backrun behind them, live; look up any wallet
- https://backrunshield.com/guides/bsc-mev — where a swap's value goes on BNB Chain, measured
- https://backrunshield.com/guides/custom-rpc — adding a custom BNB Smart Chain RPC to a wallet
- https://backrunshield.com/guides/bsc-protection-rpcs — BNB Chain MEV-protection RPCs compared, with measured latency
- https://backrunshield.com/benchmark — nine BSC endpoints measured from Tokyo every ten minutes, ours included
- https://backrunshield.com/stats — transactions protected, backruns landed, what each address is owed
- https://rpc.backrunshield.com/health — live configuration
- https://rpc.backrunshield.com/stats — the public numbers as JSON; ?address=0x… answers for one address
- https://rpc.backrunshield.com/bench — the raw measurement as JSON
- https://rpc.backrunshield.com/leaks — the last 24 h of leaks as JSON; POST {"address":"0x…"} for one wallet

## For anyone routing other people's transactions

https://rpc.backrunshield.com/r/0x<your-address> is the same endpoint with attribution attached: flow arriving through
it is recorded against that address and paid a share of what it earns. No agreement to sign, no minimum, no exclusivity.