[Merged by Bors] - Distributed POST verification

[poszu]

Part of #5185, closes #5376

• Local randomness seed to select K3 indices using p2p peer ID
• Verifying K3 indices of POST
• Verifying ALL indices for initial POST
• Publishing POST malfeasance proofs
• Verifying only the invalid index in POST malfeasance proofs
• Verify the candidate for a positioning ATX and its chain
• Verify the candidate for a commitment ATX and its chain
• Wait "some time" for malfeasance proofs before creating an active set
  ☝️ this is covered by ATX grading
• configurable duration after which ATXs (and their chains) are considered valid (in terms of POST labels)
• system tests

[codecov]

Codecov Report

Attention: 62 lines in your changes are missing coverage. Please review.

Comparison is base (ff567da) 79.5% compared to head (73fec9e) 79.5%.
Report is 1 commits behind head on develop.

Files	Patch %	Lines
common/types/malfeasance.go	18.5%	21 Missing and 1 partial ⚠️
activation/validation.go	80.5%	13 Missing and 7 partials ⚠️
sql/atxs/atxs.go	86.9%	4 Missing and 2 partials ⚠️
malfeasance/handler.go	87.5%	4 Missing and 1 partial ⚠️
activation/handler.go	84.0%	2 Missing and 2 partials ⚠️
activation/activation.go	94.8%	2 Missing ⚠️
events/events.go	0.0%	2 Missing ⚠️
datastore/store.go	80.0%	1 Missing ⚠️

Additional details and impacted files

@@           Coverage Diff            @@
##           develop   #5390    +/-   ##
========================================
  Coverage     79.5%   79.5%            
========================================
  Files          268     268            
  Lines        26591   26851   +260     
========================================
+ Hits         21146   21361   +215     
- Misses        3916    3954    +38     
- Partials      1529    1536     +7     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[dshulyak]

Wait "some time" for malfeasance proofs before creating an active set

what does it mean? active set is created at the start of the epoch. it is usually created from atxs that are graded as "good", such that were received 2 hours prior epoch start, and no malfeasance proof was received before epoch start. so effectively honest node selects atxs that could have been verified by someone during 2 hours. in cases when it is not created from grades, it will be created as a superset of activesets in the first block.

the actual problem here is that we don't have reliable sync for malfeasence proofs, so there is no guarantee that node will receive them within 2 hours from being created. this will either need to be improved before releasing distributed verification, or just be aware of this risk

[poszu]

bors try

[spacemesh-bors]

try

Build succeeded:

• ci-status
• systest-status

[poszu]

bors merge

[spacemesh-bors]

Build failed (retrying...):

• systest-status

[poszu]

bors cancel

[spacemesh-bors]

Canceled.

[poszu]

bors merge

[spacemesh-bors]

Build failed (retrying...):

• systest-status

[spacemesh-bors]

Canceled.

[poszu]

bors try

[spacemesh-bors]

try

Build failed:

• systest-status

[poszu]

bors merge

[spacemesh-bors]

Pull request successfully merged into develop.

Build succeeded:

• systest-status
• ci-status