[Merged by Bors] - beacon: handle malicious identity

[countvonzero]

Motivation

Closes #4772

Changes

for malicious identity's

• proposal: categorized as potentially valid (voting against)
• first vote: accept with weight 0
• following vote: accept with weight 0

malicious identity's weight is not included in the total epoch weight

[codecov]

Codecov Report

Merging #4779 (5e67025) into develop (6a4208b) will decrease coverage by 0.1%.
Report is 2 commits behind head on develop.
The diff coverage is 79.2%.

@@            Coverage Diff            @@
##           develop   #4779     +/-   ##
=========================================
- Coverage     76.8%   76.8%   -0.1%     
=========================================
  Files          259     259             
  Lines        29491   29522     +31     
=========================================
+ Hits         22659   22680     +21     
- Misses        5392    5400      +8     
- Partials      1440    1442      +2     

Files Changed	Coverage Δ
beacon/metrics/prometheus.go	87.7% <ø> (ø)
beacon/state.go	100.0% <ø> (ø)
beacon/beacon.go	79.4% <66.6%> (-0.1%)	⬇️
beacon/handlers.go	86.7% <100.0%> (+0.4%)	⬆️

... and 2 files with indirect coverage changes

[dshulyak]

doesn't it require grading too? otherwise how we can be sure that malicious identities are seen the same way

[countvonzero]

doesn't it require grading too? otherwise how we can be sure that malicious identities are seen the same way

i specifically asked Tal/Iddo in barcelona. they said it only requires 2 grades going into the protocol. (malicious or not) because this is tortoise style consensus. (i don't fully understand why but tortoise did only use 2 grades).

so i only count identities that are malicious before the protocol starts.

[countvonzero]

bors merge

[bors]

Build failed:

• ci-status

[countvonzero]

bors merge

[bors]

Pull request successfully merged into develop.

Build succeeded!

The publicly hosted instance of bors-ng is deprecated and will go away soon.

If you want to self-host your own instance, instructions are here.
For more help, visit the forum.

If you want to switch to GitHub's built-in merge queue, visit their help page.

• ci-status
• systest-status