Claudio
Claudio
Correct, this is the proper fix for 1704. However this still needs more testing.
Correct, this is just a temporal workaround while we implement the right solution: a special lightweight version of the history store for full nodes, that allows us to properly construct...
This problem is caused by a node that connects and has a newer macro head than the one we have, and we are currently syncing to the tip of the...
As a side effect of this issue, some misleading messages are observed during macro block production in a 4 validators + spammer + seed node docker scenario: ``` seed2_1 |...
The test scenario described in this issue is still missing.
I ran the unitest included in the _validator-stakers_ branch at various points of time, including the commit before removing LMDB and also the three devnet RC releases and in all...
Correct, reverting an unpark transaction fails if we don't have this [fix](https://github.com/nimiq/core-rs-albatross/pull/430/files#diff-7b33a1b9e51a684fa5c6dbe676f75ffb09387ae43273e1fa7a0b9fcf05a5a72cR173-R176) in place, as this [test](https://github.com/nimiq/core-rs-albatross/blob/albatross/block-production/tests/mod.rs#L212) shows.
In the last devnet run there are many instances of: `Discarding block #68320.0, we're already at macro block #884800`
Failing signature looks like this: ``` Sep 17 15:27:28 validator4 nimiq-client[915669]: 2022-09-17T15:27:28.592677Z DEBUG tendermint | Voting succeeded in round 0, assembling block. Sep 17 15:27:28 validator4 nimiq-client[915669]: 2022-09-17T15:27:28.670804Z DEBUG push...