Andrei Sandu b4dfad838c approval-distribution: aggresion must target unfinalized chain rather than unapproved chain (#2988) ...

Found the issue while investigating the recent finality stall on Westend
after upgrading to 1.6.0. Approval distribution aggression is supposed
to trade off bandwidth and re-send assignemnts/approvals until enough
approvals are be received by at least 2/3 validators. This is supposed
to be a catch all mechanism when network connectivity goes south or many
validators reboot at the same time.

This fix ensures that we always resend approvals starting with the first
unfinalized block even in the case when it appears approved from the
node's perspective.

TODO:
- [x] Versi test

---------

Signed-off-by: Andrei Sandu <andrei-mihail@parity.io>

2024-01-23 12:59:09 +00:00

..

lib.rs

approval-distribution: aggresion must target unfinalized chain rather than unapproved chain (#2988)

2024-01-23 12:59:09 +00:00

metrics.rs

Approve multiple candidates with a single signature (#1191)

2023-12-13 08:43:15 +02:00

tests.rs

Update schnorrkel to 0.11.4 (#2524)

2023-12-19 23:24:02 +00:00