You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think we should switch the VC to use (2) rather than (1). However, we should heed this comment:
Deciding how to handle it in the VC is slightly more complicated. We could switch to the standard endpoint as soon as it's available, but this would break compatibility with older versions of the Lighthouse BN. Alternatively we could wait a release or two before switching over the VC. I think I prefer switching immediately, as most users will update VC+BN together anyway.
I'm open to either strategy. If we get to implementing it in the VC before #4343 is released, then all is good. Otherwise, we're also fine.
The text was updated successfully, but these errors were encountered:
Description
We have two implementations of "liveness" detection in the BN API:
lighthouse/liveness
/eth/v1/validator/liveness/{epoch}
(implemented in [Merged by Bors] - Implement liveness BeaconAPI #4343)I think we should switch the VC to use (2) rather than (1). However, we should heed this comment:
I'm open to either strategy. If we get to implementing it in the VC before #4343 is released, then all is good. Otherwise, we're also fine.
The text was updated successfully, but these errors were encountered: