Bid on transactions
The private mempool broadcasts an auction for every transaction it receives. The auction reveals certain parts of the transaction that searchers can use to post a backrun bid.
MEVBlocker Bots: Migrating from MEVBlocker to Merkle auctions is described here: MEVBlocker compatibility
1. Listen for pending auctions
Auctions last for 1.5 second and are streamed over the following websocket:
When starting your bidder, the current list of open auctions can be fetched using the following endpoint:
http://mempool.merkle.io/auctions
Here is an example of an what an auction looks like:
2. Submit bids
Polygon is different, learn how to bid on Polygon.
Bids can be submitted using any Flashbot client with the relay url https://mempool.merkle.io/relay
. However, the first transaction needs to be the hash of the target transaction, since the full transaction data is not available to you.
The backrun transaction needs to make a Ether transfer to the fee recipient (0xe142006cd11b352a5d3be644978548f12348c91b
in this example). The value of this transfer is considered the bid amount. merkle simulates every bid to determine the amount transferred to the fee recipient.
To recap, a bid is a bundle with 2 transactions:
The hash of the target transaction
a backrun: the backrun transaction must pay the
fee_recipient
the bid with an Ether transfer.
For example, if we wanted to bid on the auction above, the bundle would be:
The full request would for this example would be:
The API responds with a bid id:
Check the status of your bid using the Bid status API endpoint.
Last updated