Implement liveness BeaconAPI
#4243
Labels
Comments
|
Yeah we do! There's an existing liveness endpoint that our doppelganger detection uses, so implementing the standard API should just be a straight-forward port of that: https://lighthouse-book.sigmaprime.io/api-lighthouse.html#lighthouseliveness. 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. |
michaelsproul
added
good first issue
|
Thanks! I edited the ticket description with the good link! (I copy/pasted the wrong one.) |
bors bot
pushed a commit
that referenced
this issue
Jul 31, 2023
## Issue Addressed #4243 ## Proposed Changes - create a new endpoint for liveness/{endpoint} ## Additional Info This is my first PR.
|
Completed in #4343 |
Woodpile37
pushed a commit
to Woodpile37/lighthouse
that referenced
this issue
Jan 6, 2024
## Issue Addressed sigp#4243 ## Proposed Changes - create a new endpoint for liveness/{endpoint} ## Additional Info This is my first PR.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
Beacon API
v2.4.0defines a liveness endpoint (in some ways similar to this).Does the Lighthouse team plan to implement it?
EDIT: Replace link in "in some ways similar to" by the good one.
The text was updated successfully, but these errors were encountered: