Regarding using BloXroute relay proxies, we made a change to our architecture, where validators don’t need to run any local components, yet can still connect to a relay proxy. We now allow validators to use relay proxies in many regions throughout the world (US, EU, Singapore, Hong Kong, Tokyo, Sydney, and Dublin) without having to run their own. These proxies communicate with the relay using gRPC, and are faster than communicating with the relay directly. Validators using relay proxies receive higher paying blocks than those who don’t, due to the validator being able to receive blocks built later in the slot because of the reduced builder-to-proposer latency. While the proxy appears as an additional relay, the backend relays are the two bloXroute relays that are approved by the Lido community. In the future, additional relays will integrate with the relay proxies.
Info
-
More info is available here: Validator Gateway | bloXroute Documentation
-
Source code for the relay proxies is available here: GitHub - bloXroute-Labs/mev-relay-proxy-external
-
Holesky Relay Proxy: http://54.164.127.218:18552
-
Google Meet call for interested node operators: Wednesday, July 31 · 17:00-18:00 UTC, https://meet.google.com/qqd-muju-eas