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
{{ message }}
This repository was archived by the owner on Mar 18, 2026. It is now read-only.
when we detect we are X blocks behind from chainhooks and the pull system kicks in, we should send a Discord message or some kind of alert to check on things
somewhere around here (from logs):
Oct 27 20:24:21 2025-10-27 20:24:21 | INFO | chain_state_monitor | Current API block height | task=chain_state_monitor api_block_height=3627998
Oct 27 20:24:21 2025-10-27 20:24:21 | INFO | chain_state_monitor | Current DB block height | task=chain_state_monitor db_block_height=3627997
Oct 27 20:24:21 2025-10-27 20:24:21 | INFO | chain_state_monitor | Chain state is blocks behind the current chain tip | task=chain_state_monitor blocks_behind=1 db_block_height=3627997 api_block_height=3627998
Then if blocks_behind>10 or whatever the target is when the pull system kicks in, queue a message
when we detect we are X blocks behind from chainhooks and the pull system kicks in, we should send a Discord message or some kind of alert to check on things
somewhere around here (from logs):
Then if
blocks_behind>10or whatever the target is when the pull system kicks in, queue a message