This is a follow-up fix of PR #78. In both cases, a script should validate all the keep-client versions in a given reward interval. If it happens that a client runs an older version that is allowed it should not be eligible for rewards.
In this scenario when a cutoff day for the upgrade enters the next rewards distribution a staker can run either of two latest client versions at any given moment.
This is a follow-up fix of PR #78. In both cases, a script should validate all the keep-client versions in a given reward interval. If it happens that a client runs an older version that is allowed it should not be eligible for rewards.
In this scenario when a cutoff day for the upgrade enters the next rewards distribution a staker can run either of two latest client versions at any given moment.
No prior distributions were affected.