auricom

Today the readiness endpoint only checks “blocks behind best-head ≤ X”. However the result of this metric is tightly coupled to the internal sync-loop implementation; The goal we should aim...

Logs from sept. 10 about how the erratic behavior ``` # ev-node 2:40PM INF syncing header and data component=BlockManager height=3016 2:40PM INF syncing header and data component=BlockManager height=3016 2:40PM ERR...

A healthcheck endpoint is used by infrastructure automation to determine if a process can respond to client requests. AFAIK based on this PR, the existing endpoint did not perform substantive...

the included documentation does seem to be what we want to achieve, thanks but i'm not sure the ready endpoint is working as intended ran a fullnode on eden testnet...

turns out that was issues coming from my workstation. Can confirm that unready node was detected unready on the endpoint