Skip to content
You are reading the Teku development version documentation and some features may not be available in the stable release. You can switch to the stable version using the version box at the bottom of the screen.

Updated on August 11, 2022

Builder network and MEV-Boost

When The Merge completes, consensus clients will be responsible for proposing blocks containing an execution payload obtained from their local execution clients via the Engine API.

A consensus client can optionally configure an external builder and delegate the execution payload construction to it, instead of using the execution client.

MEV-Boost

The most common builder deployment is to run a specialised external software such as MEV-Boost. MEV-Boost works by requesting a payload proposal from several entities (called relays), and selecting the best bid in order to improve validator rewards and increase the maximal extractable value (MEV).

Teku allows you to configure the beacon node to use a builder network to generate execution payloads. In case of failures or non-timely responses, Teku will fall back to the payload produced by the local execution client specified with ee-endpoint.

Questions or feedback? You can discuss issues and obtain free support on Teku Discord channel.