The team at Blocknative has worked on relay improvements to help validators reduce their occurrence of orphan slots.
If the proposing validator takes too much time to submit their block to their beacon node, the next proposing validator may not receive the data in time (ie: the block doesn’t reach them fast enough). This results in a fork and an orphaned slot. More info can be seen here regarding orphan slots.
In order to help validators reduce their instance of orphaned slots, we recently implemented a flag that synchronously publishes blocks to the beacon chain to reduce syncing issues. As soon as
getPayload is requested the Blocknative Relay publishes the block to its beacon node.
What you need to know
No action is needed by Validators - this is done automatically.