False notice when relay publishes unblinded block ahead of beacon node about nimbus-eth2 HOT 3 CLOSED

It might be worth simply removing from the Nimbus builder API handling code the broadcast -- initially it was required. I tested without it and it didn't work at all.

Then it was about equal -- nice, but unnecessary.

Now, I'm not sure it makes sense at all, since the relays are adding unblinding delays to protect themselves.

The blocking issue there is that they also aren't required to by the builder API spec, and as such, technically Nimbus MEV blocks might just not get out at all and technically it'd be Nimbus's fault.

So removing the broadcasting code entirely doesn't make sense until/unless the builder specs explicitly require this.

from nimbus-eth2.

Now, I'm not sure it makes sense at all, since the relays are adding unblinding delays to protect themselves.

We might as well publish it if we haven't received it from gossip: this is good for latency since the block will then propagate faster - gossipsub will take care of deduplication, if needed.

from nimbus-eth2.

#4904

from nimbus-eth2.