MEVBlocker compatibility

This tutorial is for searchers who are already biding on MEVBlocker auctions and would like to bid on Merkle auctions as well.

In order to make the transition easier, we have a MEVBlocker-style websocket that migrating searchers can use:


The data format of the websocket is identical to MEVBlocker with one difference. For Merkle auctions, a new parameter feeRecipient is added to transactions. For example, here is an auction on Merkle:

  "jsonrpc": "2.0",
  "method": "eth_subscription",
  "params": {
    "result": {
      "accessList": [],
      "chainId": "0x1",
      "data": "be9a6555",
      "from": "0x90bacaaA622a1810cfafe60812dD4CaB98cb2C4D",
      "gas": "0x16734",
      "hash": "0xef4acec843ebb56a9ace1086f204e5bbf1208b2b25157a1e17acfa6ca9d6d18b",
      "maxFeePerGas": "0x0",
      "maxPriorityFeePerGas": "0x0",
      "nonce": "0x3",
      "to": "0x0526269FB16e9bD48846ba5363D872038887Bf6B",
      "type": "0x2",
      "value": "0x0",
      "feeRecipient": "0x1E8e81dC3B221885b386e3d1c9efe93fc2863B24",
      "logs": [
          "address": "0x0319000133d3AdA02600f0875d2cf03D442C3367",
          "data": "0x",
          "topics": [
    "subscription": "0x00000000000000000000000000000000"

All bids should pay the feeRecipient instead of the block builder.

Bundle can be submitted as usual, either through the websocket or through our relay

Join the discord for searcher support.

Last updated