CLI flag to hardcode timestamp for validator registration

[terencechain]

We might need a flag that enables validators to hardcode the timestamp in the registration schema. This may be required for distributed validators to come to a consensus. Today's implementation we are using the current timestamp which will be different on each co-validator.

[nisdas]

This seems like the wrong approach, why do we need to hardcode the timestamp like this ? Why does validator registration require signing a timestamp ?

[terencechain]

For distributed validators, it's important that the signed registration are the same across all "co-validators", current timestamp is likely to never match across multiple validators. The common resolution on other validator clients so far has been to include a -builder-timestamp-override flag that enables the user to hardcode a value. Both teku and lighthouse support this. It is then used for every subsequent re-registration