Flashbots Protect routes MetaMask transactions privately
To connect MetaMask to Flashbots Protect, add its RPC URL to Ethereum Mainnet, select it, then confirm a small test transaction on Etherscan.
By The Blocktide Editors4 min read
Add Flashbots Protect’s RPC URL to Ethereum Mainnet in MetaMask first; every transaction uses the RPC selected for that network. To complete the setup, add https://rpc.flashbots.net as an extra RPC URL on the existing Ethereum Mainnet network, keep chain ID 1, and select the endpoint; MetaMask then routes the next transaction through Protect. Protect’s one-click Add to MetaMask option is available on Flashbots.
An RPC endpoint is the server address MetaMask uses to read the chain and broadcast transactions. The chain ID identifies which chain the wallet is using; Ethereum Mainnet is chain ID 1. Flashbots is a research and development organization focused on MEV in Ethereum, and Protect is part of its transaction infrastructure.
Add Protect as an RPC option on Ethereum Mainnet
Have these ready before changing the network settings:
- MetaMask installed and set to Ethereum Mainnet.
- A small ETH balance to cover the test transaction’s gas.
- The Protect RPC URL: https://rpc.flashbots.net.
- Open the network settings. In MetaMask, open Settings, then Networks, and edit Ethereum Mainnet. The visible result should be the settings for the existing mainnet network, including its RPC options.
- Add Protect’s URL to that network. In the RPC URL options, choose Add RPC URL and enter https://rpc.flashbots.net. Save it as an additional endpoint, with chain ID 1 and ETH as the currency. The endpoint should now appear as an option for Ethereum Mainnet.
- Select the Protect endpoint. Set the new URL as the default RPC for Ethereum Mainnet, then save. MetaMask should show the Protect endpoint as selected while the network remains Ethereum Mainnet.
- Send a small test transaction. Make a modest transfer to an address you control, review the details in MetaMask, and confirm it. The task is complete when the transaction confirms on Etherscan while the Protect endpoint remains selected.
There is one common snag: MetaMask may say that chain ID 1 is already in use. That is because Ethereum Mainnet already uses that identifier. Keep the existing network and add Protect as another RPC URL within it; don’t try to create a second Ethereum Mainnet entry with the same chain ID. The point is to change the gateway MetaMask uses, not the chain the wallet is on.
For a quick setup, the Add to MetaMask button on the Protect site can add the endpoint through a wallet prompt. Approve the prompt, then make sure the resulting Protect RPC is selected for Ethereum Mainnet. The manual route makes the same change through network settings and is useful when you want to enter the endpoint yourself.
Say you are about to send a small ETH transfer. You add the URL, save it on the existing mainnet network, and select it. MetaMask continues to show Ethereum Mainnet, but the selected RPC is now Protect. After confirming the transfer, you look up its transaction on Etherscan. A confirmation there, with Protect still selected in MetaMask, verifies both the transaction and the setup.
Related MetaMask and Protect questions
Is Flashbots Protect safe to use with MetaMask?
Protect is designed to route Ethereum transactions privately, and MetaMask remains where you review and sign each transaction. Selecting an RPC changes the endpoint used to send transactions; it does not remove the need to check the recipient, amount, and fee details before approving. For this setup, confirm you are on Ethereum Mainnet and have selected the intended Protect URL before sending.
How do I switch MetaMask back to the default RPC?
Open Settings, go to Networks, and edit Ethereum Mainnet. In its RPC URL options, select MetaMask’s default endpoint instead of Protect and save. The network stays on Ethereum Mainnet; only the selected RPC changes. Before sending again, check that MetaMask shows the endpoint you intend to use.
What to know after connecting Protect
Does Flashbots Protect work on other networks besides Ethereum?
This setup is for Ethereum Mainnet. Another chain requires an endpoint and configuration for that chain; the Ethereum Mainnet URL and chain ID 1 should not be assumed to apply elsewhere. Check current availability for the network you intend to use before changing MetaMask.
Does Flashbots Protect cost extra gas?
Ethereum transactions still require gas, and the fee depends on the transaction and network conditions. Sending through an RPC does not remove that requirement. Review the fee MetaMask displays before signing; the endpoint selection is a routing choice, not a substitute for checking transaction costs.
Can I use Flashbots Protect with a hardware wallet in MetaMask?
If your hardware wallet is connected to MetaMask, the RPC choice is still made in MetaMask’s network settings, while transaction approval remains with the wallet. Select the Protect endpoint for Ethereum Mainnet, then review and approve the test transaction on your hardware wallet as usual. Confirm it on Etherscan before relying on the setup for a larger transfer.