MEVBlocker Compatible (V3)
Last updated
Last updated
The V3 WebSocket is an extension of the V2 Websocket so please refer to that for core functionality this page highlights the differences / additions.
During the initial development of Blink, searchers will need to be onboarded for access. Searchers should reach out to or @YNBlink / @ciaranmcveigh on telegram or discord for access.
You can connect to Blink's WebSocket via wss://ethauction.blinklabs.xyz/ws/v3/{$API_KEY}
Below are the differences between the V3 and V2 websockets.
The V2 websocket auto-subscribed you to the transaction flow. V3 will require eth_subscribe to have been called to begin streaming data.
The are 2 flows you can subscribe to, transactions and "originator bundles".
"Originator Bundles" are non-searcher bundles, an example of one would be a telegram bot that is sending a bundle with an approve ERC-20 & swap ERC-20 so that can be executed sequentially in the same block [ approveTx, swapTx] .
Transactions can be subscribed to using either
Originator bundles can be subscribed to using either
You can also subscribe to multiple data streams at once
The V3 websocket gives you access to originator bundles data streams that can be searched on. The same principles apply as with individual txs, the searcher tx must go after the "originator bundle".
The MEVBlocker Schema will again be used for exposing the data with one slight change. Result will change from a single tx JSON object to an array of tx JSON objects.
Here's an example
The bidding process is the same as for a normal transaction, you can submit via
The corresponding bundle will be found and the searcher txs will be appended before being sent to the builders.