Use a private RPC for every transaction or only swaps: a simple rule
Use a private RPC for every transaction or only swaps? Route transactions with a price or a race privately; use either RPC for routine transfers and approvals.
The Splyt Genesis Desk

Use a private RPC for swaps, mints, claims and other transactions with a price or a race to win; plain ETH transfers and approvals can use either. Flashbots Protect routes transactions privately, helping keep extractable activity away from the public mempool.
Choose by MEV exposure, speed and switching effort
MEV exposure: A swap can be sandwiched: someone sees it in the public mempool and places trades around it to profit from your transaction. Liquidation repays, competitive mints and airdrop claims can also be front-run when timing or a price advantage matters. Route those through a private RPC. A plain ETH transfer or approval has no trade price or race to win, so there is little to extract from it.
Flashbots Protect is a concrete fit for this choice because its private transaction routing keeps those exposed transactions out of the public mempool; flashbots relay is the relevant feature. Use it when the transaction could be targeted for its value or timing.
Inclusion speed: A public RPC may be the better choice when your priority is speed for an ordinary transaction. Private routing can occasionally mean slower inclusion. For a swap or competitive mint, that trade-off may be worthwhile because the transaction is more exposed to extraction in the public mempool.
Compare two transfers under the same conditions: same wallet, network, amount and need to send promptly. If one is a plain ETH payment, either RPC is reasonable. If the other is a swap, route it privately: the deciding difference is the price and sandwich risk, not the amount or urgency.
Switching effort: A wallet uses one RPC per network for every transaction it sends. So “private RPC only for swaps” means changing the network’s RPC before each swap, then changing it back for ordinary activity. If you forget, an exposed swap can go through the public mempool.
You can save the Protect RPC as a second network entry and switch to it with one click when a transaction has MEV exposure. Or keep it as the default and switch to a public RPC only when you need speed for a routine transaction. Flashbots does not charge users a fee for sending transactions through Protect, so using it for everything costs nothing in fees; the trade-off is occasional slower inclusion.
Who each option suits: Use a private RPC for swaps only if you are comfortable switching networks and remember to do it before exposed transactions. Use it for everything if you sometimes forget to switch. That gives you a simple default for swaps, claims, mints and repayments, while accepting that a routine transfer may occasionally take longer.
Related
Does a private RPC slow down plain ETH transfers?
It can occasionally mean slower inclusion. If the transfer is routine and speed matters, use the public RPC; if convenience matters more, leaving the private RPC on avoids a switch.
Is a private RPC useful for NFT mints?
Yes, when the mint is competitive. Other participants may race for the same opportunity, so private routing can reduce exposure to front-running. For a mint with no timing or price competition, either RPC can work.