Can switching RPCs expose a previously private swap?

Yes, switching submission paths can expose an already signed private transaction publicly. Whether that happens depends on the wallet and service, so check their documented behavior before changing RPCs during a pending swap.

Flashbots specifically warns MetaMask users that switching RPCs before confirmation can cause public rebroadcast. This is a concrete product warning, not a claim that every wallet behaves identically.

Why the old transaction still matters

The signed request remains the same authorization even if one private service stops trying to include it. A dropped status does not erase copies of the payload. Public rebroadcast can make its route and amount conditions visible to a different set of participants.

Resolve the pending state first

Check the original hash, sender nonce and service status. Use the service’s supported cancellation or stuck-transaction guidance. Flashbots provides a dedicated troubleshooting page for that context.

If you choose public submission, understand that you are changing the protection assumptions. Review whether the original deadline and amount bounds still make the transaction acceptable.

Avoid accidental duplicate trades

Creating a fresh swap with another nonce is separate from rebroadcasting the existing transaction. Both can potentially execute if their conditions remain valid. Track the original and any replacement before deciding the account is clear.

Do not assume a “MEV protected” label survives every fallback, manual fee action and endpoint change. The protection belongs to a particular submission path and configuration.