Describe the bug
We're encountering an issue on both Holesky and Mainnet where, after updating the fee recipient address of a validator via the VC, the change sometimes doesn't appear on the relay. We're using the Relay Data API to verify if the address has been updated.
Steps to reproduce
Jun 11th 16:25UTC: we've switched the fee recipient address for 0x8068ae109fed6a4cb0ce91f192a0988dfb7c2a66a3a46878e233386f4f0dd9ad57f94c1782652534d4d6e7c3a7732753 from 0x8bc0e8f415618ed2938d9a1d737e9045e65c2de8 to 0xf60e717ce428e7d1d61e147aa34f1595caa56669, and the change was picked up by the relay
Expected behavior
We expect the change to the fee recipient address to be reflected on the relay as soon as the next batch of registrations happens (we're using Lighthouse, so that happens every epoch).
Describe the bug We're encountering an issue on both Holesky and Mainnet where, after updating the fee recipient address of a validator via the VC, the change sometimes doesn't appear on the relay. We're using the Relay Data API to verify if the address has been updated.
Steps to reproduce
0x8068ae109fed6a4cb0ce91f192a0988dfb7c2a66a3a46878e233386f4f0dd9ad57f94c1782652534d4d6e7c3a7732753from0x8bc0e8f415618ed2938d9a1d737e9045e65c2de8to0xf60e717ce428e7d1d61e147aa34f1595caa56669, and the change was picked up by the relayExpected behavior We expect the change to the fee recipient address to be reflected on the relay as soon as the next batch of registrations happens (we're using Lighthouse, so that happens every epoch).
Which version are you using: We're using Lighthouse v5.1.0 for the VC and BN. Relays are https://boost-relay-holesky.flashbots.net/ and https://boost-relay.flashbots.net/
Additional context The issue seems to be very similar to the one described in this PR https://github.com/flashbots/mev-boost-relay/pull/167