bloXroute Validator Gateway

Integration
1

The GMC recently met with bloXroute to learn about their Validator Gateway product, which has the potential to enhance effectiveness across Rocket Pool validators. Example data can be viewed at https://relayscan.io/

bloxRoute is a blockchain distribution network that gave a presentation at Rocket Pool’s Denver Lift-Off event. That video can be viewed here.

Validator Gateway (Validator Gateway | bloXroute Documentation)

  • Relay Proxy A free service co-locating the relay with the node operator, streaming block bids to node operators in real-time. You can set the timing for accepting bids within a slot.
  • Blockchain Distribution Network (BDN) A paid service utilizing data stripping to send data via direct routes. Once a validator node accepts a block bid, the BDN ensures rapid propagation across the network. For duties like attestations or sync committees, the BDN Gateway helps keep nodes synchronized with the current head slot, enhancing validator effectiveness and increasing high-paying attestations within block proposals. The BDN Gateway aims for near 100% effectiveness.

Some Questions That Were Answered

  • How would it work for small solo stakers?
    Relays can be set up regionally, and they can be purchased in various locations.

  • How many relays would make sense for the entire US?
    Possibly one per state, or fewer if that is excessive.

  • What happens if a relay goes down?
    There is no risk, as connectivity to other relays remains.

  • Is it only profitable when maximizing timing games?
    Node operators can manage risk by setting delays.

Payment and Billing
The GMC is interested in the fixed price per pubkey option. bloXroute is willing to accept RPL as payment.

The GMC is seeking the pDao’s input. Please ask any questions you have below, or provide any feedback.

–

Should the Smart Node integrate the bloXroute Validator Gateway?

  • Yes
  • No
0 voters
1 Like
2

I’m pretty unsure about this. Better effectiveness for Rocket Pool sounds good. But bloXroute is one of the worst relays when it comes to trying to use their public API endpoints, so I feel biased against them. And I would like to understand the centralisation and other risks here better before signing off. That’s why I voted no. It feels shady because of the brand and the money involved, but I want more analysis of risks to make an informed choice.

2 Likes
3

Relay Proxy seems unremarkable in the sense that bloXroute is already an approved relay, and having better RTT is a strict improvement.

I’d prefer for the BDN decision to fall to individual node operators, who can opt to pay for it. I don’t think it’s sensible for the pDAO to socialize the cost. I do think we should gauge pDAO sentiment before trying to integrate smart node.

I mentioned to bloXroute in Denver that RP NOs receive partial income per public key and the pricing is less attractive unless it accounts for that.

1 Like
4

It’s not clear to me what we’re voting on. Is there a concrete proposal with costs? Or it more of a vibe check? (or is the video the proposal, which I haven’t watched?)

5

It’s more of a vibe check at this point. The GMC was considering paying the costs, but it depends on the feedback received from the DAO.

6

I’ll start by caveating that I think my understanding is at like a 5/10 here. This may be its own issue, but it does mean a large bit of salt is appropriate when reading the rest.

My gut feel on BDN is that it creates a second source of truth. If it’s wrong it can cause slashing etc (either direction depending how popular BDN is). If it’s right, it’s providing a more-profitable move than using spec consensus. Bugs me at the ethos level

The relay collocation sounds helpful. That said… I’m rather confused why this isn’t the default behavior? Like wouldn’t it be good for all parties to have a “US east” sorta thing? Variants of this have even used source IP to decide what server to point you at for a given domain. What I’m asking here in context amounts to “why should RP pay this?” If this is cheap enough, sure why not, but I would definitely want to feel very comfortable that we come out ahead (even if bloxroute prevalence changes quite a lot).

7

I’m also somehow like ramana and just don’t like bloxroute. They have two relays, one “max profit” and one “regulated”. However, at some point they changed the “max profit” one to also censor:

bloXroute hosts two types of MEV relays, Max profit and Regulated, that validators and builders can connect to. Both two relays currently propagate all available transactions/bundles except the ones that interacted with addresses sanctioned by OFAC, and they have the same filtering requirement, although for legacy reasons, bloXroute still maintains the two relay names in parallel.
(MEV Relay (For Validators) | bloXroute Documentation)

This makes everything bloxroute does very uncertain. They might start with something ok and then decide to censor stuff, gaslighting their customers…