See node tank-0012-aqua. According to fork-observer it is actually in sync with the miner's chain tip (1457). The node-data also supports this, showing the correct tip as the "active" chain.
However, the first chaintip in the array is an inactive fork at a much lower height (806), which is interesting, but it is not accurate to report that node as being "stuck" at that height.
I suspect the issue is this line:
|
const blocksBehind = latestTipHeight - tips[0].height; |
Once this is patched, we'll need to apply to the plugin branch and deploy a new image for warnet
See node tank-0012-aqua. According to fork-observer it is actually in sync with the miner's chain tip (
1457). Thenode-dataalso supports this, showing the correct tip as the "active" chain.However, the first chaintip in the array is an inactive fork at a much lower height (
806), which is interesting, but it is not accurate to report that node as being "stuck" at that height.I suspect the issue is this line:
warnet-web/src/components/node-group-cards.tsx
Line 40 in 2933a9e
Once this is patched, we'll need to apply to the
pluginbranch and deploy a new image for warnet