GetBlock Adds MEV Protection: What to Know

GetBlock, a leading provider of RPC nodes and Web3 infrastructure, has announced a major expansion of its service offerings.

It now provides fully MEV-protected RPC endpoints for Solana, Ethereum, BNB Smart Chain, and Base blockchains.

Here’s what’s especially cool: MEV protection is integrated directly at the RPC endpoint layer. There’s no need for extra development work to secure your dApp any longer.

MEV-protected RPC endpoints now available for Solana, Ethereum, BSC, Base

Starting May 2025, GetBlock’s RPC API endpoints will come with built-in MEV protection. This eliminates the need to build in-app defenses - your dApp is protected right out of the box.

This functionality is made possible through a partnership with Merkle, pioneers in MEV protection. The setup routes transactions through private mempools, adding a layer of obfuscation. In this architecture, Merkle acts as a trusted private builder.

With private mempools on Solana, Ethereum, Base, and BNB Smart Chain, MEV bots are blocked from detecting and sandwiching legitimate user transactions.

Currently, MEV-protected private RPC endpoints are available for shared node packages on these four blockchains. A fully protected dedicated node offering is currently in development.

Getting started with MEV-protected RPC

As mentioned earlier, GetBlock customers can access MEV-protected RPC endpoints the same way they use regular ones. In fact, it only takes three simple steps:

1. Create an account on GetBlock and log in. You can sign in using MetaMask, Google, GitHub, or email.
2. Go to the Shared Nodes endpoints menu.
3. Get your MEV-protected RPC endpoint. Choose your blockchain (Ethereum, Solana, BSC, or Base), set the network type to “Mainnet,” select the endpoint type “MEV-Protected JSON RPC,” and click “Get.”

Image by GetBlock

That’s it! You can now integrate the endpoint directly into your dApp’s codebase.

Note: Users on the free plan must upgrade to a paid plan to access MEV-protected RPCs.

Here’s what happens under the hood: everything functions just like a regular RPC endpoint. Sending transactions to EVM-compatible blockchains through a private, MEV-protected RPC works in exactly the same way, with no changes needed on your end.

POST https://go.getblock.io/
Content-Type: application/json

{
  "jsonrpc": "2.0",
  "method": "eth_sendRawTransaction",
  "params": [
    "0x02f8...abc"  // your signed transaction here
  ],
  "id": 1
}

Once your request is authorized, the transaction is relayed to a private mempool instead of the default public one.

GetBlock and Merkle are currently collaborating on a technical deep dive that will explore the details of our joint MEV protection architecture.