pventuzelo
changed the title
[FUZZ] Prysm mismatch when processing ProposerSlashing (ProposerNotSlashable error expected)
[FUZZ] Prysm mismatch when processing ProposerSlashing (error expected: ProposerNotSlashable)
Nov 4, 2020
FYI, Prysm was using an incorrect epoch when validating the slashing.
Instead of using the current epoch in the beacon state, they was using the proposer_slashing's epoch.
I will test the fix and update the internal pfuzz lib today
Beaconfuzz_v2 just found a ProposerSlashing that is interpreted differently by eth2 clients:
Info to Reproduce
Download: issue_prysm_ProposerNotSlashable.zip
Run:
Your Environment
The text was updated successfully, but these errors were encountered: