[Bug] Internal Discarded block, a node unable to recover

[al-onyxprotocol]

Summary

Node continuously discards blocks and is unable to recover. Nodes regularly output discarded block warnings.

Steps to reproduce

Issue 1

Node: 199.192.25.77
Problem: Node continuously discards blocks and is unable to recover.

Logs example:

0|adamant  | [WRN] 2025-09-03 18:17:21 | Discarded block that does not match with current chain: 467729197334300668 height: 48556431 round: 480757 slot: 50510368 generator: 61455504cd279603970c6ce19f7ae5eaf1ce077eca162f125ef00c2d046902c7
0|adamant  | [WRN] 2025-09-03 18:17:21 | Discarded block that does not match with current chain: 467729197334300668 height: 48556431 round: 480757 slot: 50510368 generator: 61455504cd279603970c6ce19f7ae5eaf1ce077eca162f125ef00c2d046902c7
0|adamant  | [WRN] 2025-09-03 18:17:21 | Discarded block that does not match with current chain: 467729197334300668 height: 48556431 round: 480757 slot: 50510368 generator: 61455504cd279603970c6ce19f7ae5eaf1ce077eca162f125ef00c2d046902c7

Notes

The problem with the 199.192.25.77 node is that delegate vote weights are different compared to the network, even though it doesn’t have any missing vote transactions.

Issue 2

Nodes: "lake" and "clown"
Problem: These nodes regularly output discarded block warnings.

Logs example

1|adamant  | [WRN] 2025-08-29 11:43:34 | Main queue - 1870
1|adamant  | [WRN] 2025-08-29 11:43:35 | Main queue - 1869
1|adamant  | [WRN] 2025-08-29 11:43:36 | Discarded block that does not match with current chain: 16287999137438390951 height: 48475758 round: 479958 slot: 50419217 generator: fdca8bc798e8922cdd4a7745f1ec70e3d0dbea01ab14d31ca7618ec0c296b98f
…
1|adamant  | [inf] 2025-08-29 11:43:38 | Received new block id: 16294187716859600075 height: 48475760 round: 479959 slot: 50419219 reward: 15000000
1|adamant  | [inf] 2025-08-29 11:43:40 | Broadhash consensus now 0 %

Expected behavior

To Do

• Investigate why nodes discard blocks and fail to recover
• Check consensus/vote weight mismatch on node 199.192.25.77. Push a fix.
• Analyze "lake" and "clown" nodes for stability and block sync issues. Push a fix.
• Describe what is “Main queue” log record, why it’s so often, and why it’s WRN type

Actual behavior

See "Steps to reproduce".

Screenshots or videos

Environment

Node v0.10.0 (dev)

See also

https://github.com/orgs/Adamant-im/discussions/25

[yoxira]

Regarding the "Issue 1", the problem should be already fixed (CHANGELOG).

[yoxira]

Describe what is “Main queue” log record, why it’s so often, and why it’s WRN type

We have a queue for loading and processing blocks. If the node receives too many blocks and struggles to process them, the queue can grow too long, logging the warning. This situation can be caused by slow database reads or CPU lag.