Closed Daft-Wullie closed 3 years ago
FYI, that the same file and issue than https://github.com/sigp/beacon-fuzz/issues/82 but this time it's teku that return a different result than the others.
For analysis, here is a package containing the pre state, the proposerslashing and the post state generated by teku.
issue_90_proposer_slashing.zip
lighthouse reject this proposerslashing processing with the error: ProposalsIdentical prysm reject the proposerslashing processing nimbus reject the proposerslashing processing teku process the proposerslashing processing
You can reproduce with:
../beaconfuzz_v2 debug beacon.ssz propslash.ssz proposerslashing
Thanks @Daft-Wullie
Confirmed to be the same type of discrepancy described in #82. For its process_proposer_slashings
function, Teku compares the SignedBeaconBlockHeader
s, instead of the BeaconBlockHeader
s.
I've done and provided the following:
[FUZZ]
issue already refers to that crasherbeacon-fuzz
version or commit used.Info to Reproduce
Command run: e.g.
make fuzz-all
Crasher file name: crash-8aca1b5ce295f678fb67bd5ea8bb36c13a0d7f20 crash-8aca1b5ce295f678fb67bd5ea8bb36c13a0d7f20.zip
Client exercised: Teku
Fuzzing engine used (if applicable):
Crash output and stacktrace
Your Environment