When running ordhook and ordinals-api on a server, I encountered an issue related to data synchronization between the two components. ordhook is expected to send blockchain data to ordinals-api up to the latest indexed block. However, under certain conditions, ordhook only sends data up to a slightly older block, this leads to synchronization gaps and errors in data processing.
Current Behavior:
ordhook has synchronized blockchain data up to the latest indexed block (#848288) at 2024-06-17T06:04:14.616469649Z.
ordinals-api begins registering predicates from block #848277 at 2024-06-17T06:10:46.694234931Z.
While ordhook is transmitting data to ordinals-api, a new block (#848289) is mined on the network at 2024-06-17T06:13:15.61295629Z.
Despite the availability of block #848289, ordhook only sends data up to block #848288 and logs the following:
Description
When running ordhook and ordinals-api on a server, I encountered an issue related to data synchronization between the two components. ordhook is expected to send blockchain data to ordinals-api up to the latest indexed block. However, under certain conditions, ordhook only sends data up to a slightly older block, this leads to synchronization gaps and errors in data processing.
Current Behavior:
ordhook
has synchronized blockchain data up to the latest indexed block (#848288) at 2024-06-17T06:04:14.616469649Z.ordinals-api
begins registering predicates from block #848277 at 2024-06-17T06:10:46.694234931Z.While
ordhook
is transmitting data toordinals-api
, a new block (#848289) is mined on the network at 2024-06-17T06:13:15.61295629Z.Despite the availability of block #848289,
ordhook
only sends data up to block #848288 and logs the following:After receiving block #848290,
ordhook
resumes sending data toordinals-api
, skipping block #848289 entirely.This behavior causes
ordinals-api
to miss block #848289, leading to the error "Block inscription gap detected".Expected Behavior:
ordhook
should consistently send blockchain data toordinals-api
up to the latest indexed block (#848289)Additional
The issue does not occur when
ordinals-api
starts and receives data fromordhook
whithout new blocks being mined during the processEnvironment:
Ordhook docker image: hirosystems/ordhook:2.1.0