Under some circumstances fee-recipient is not taken into account about prysm

[nisdas]

@aimxhaisse There has been an API change in v4.2.0, so we highly recommend running a v4.2.0 beacon with a v4.2.0 validator client. Otherwise you might run into the edge cases described above:

From our release notes

Upgrading / Downgrading Validators
There are some API changes bundled in this release that require you to upgrade or downgrade in particular order. If the validator is updated before the beacon node, it will see repeated 404 errors at start up until the beacon node is updated as it uses a new API endpoint introduced in v4.2.0.

🔼 Upgrading: Upgrade the beacon node, then the validator.
🔽 Downgrading: Downgrade the validator to v4.1.1 then downgrade the beacon node.

[aimxhaisse]

Thanks for the quick response, this actually happened during an upgrade following the recommendations (i.e: just after upgrading the beacon to v4.2.0 and before upgrading the validators). I'll try to trigger it with both BN and VC in v4.2.0.

[aimxhaisse]

We weren't able to reproduce it so far, marking as closed but may re-open if we see it again.