Assumptions
The assumption is that bothVouch
and MEV Plus
have been installed. If not, please consult the following guides:
Base MEV Plus configuration
MEV Plus configuration should look something like this:- Sets MEV Plus’ listen address and port to
http://0.0.0.0:18551
which theConsensus Builder API
will talk to - Acknowledges MEV Boost is operating on address and port
http://X.X.X.X:18550
ensuring normal operation - Will access general beacon node information from
http://127.0.0.1:5052
and, - Will broadcast smart contract transactions to the exeuction layer on
http://127.0.0.1:8545
Vouch communication with MEV Plus
MEV Plus will communicate with Vouch via the existing Boost configuration parameterswithout
affecting any communication with Boost. Here’s an example Holesky
config (please not it may not be complete):
- MEV_BOOST_URL=http://0.0.0.0:18551
- ENABLE_MEV_BOOST=true
ENABLE_MEV_BOOST=true
and the URL pointing to Plus, then both Plus and Boost will work and MEV Plus logs will look something like this:
- They are all using the same suggested fee recipient on the node
- If an inclusion list was defined then only the validators in that list will be natively delegated (it is possible to include validators by fee recipient or specify individual addresses)
- If an exclusion list was defined then all validators apart from excluded ones will be included