Closed liveactionllama closed 7 months ago
Note: per discussion with the judge, sponsor, and participating wardens, the full scope for this competition was initially a bit unclear. As such, the participating wardens have all agreed to review items outside of the original active competition phase. Adding their work to this findings repo for further review by all parties.
My 2 cents: if the event would current emit:
Then the refactoring is not necessary
Yes, it is implemented as @GalloDaSballo suggested, staker and stakee are the same on selfSlash and different on communitySlash
Yes, it is implemented as @GalloDaSballo suggested, staker and stakee are the same on selfSlash and different on communitySlash
I suggest ignoring the suggestion then!
GalloDaSballo marked the issue as nullified
This adds a missing Release event and changes the Slash event.
Description
The owner implemented a missing address to correspondent the slashed stakee in case of a community stake slashing.
Currently the slashing function can emit a slashing event which depends on the kind of executed slash.
The main problem we are facing is that it's hard to differ whether a self or community stake was slashed:
Recommendation
l recommend emitting two different events depending on the situation of which kind of stake is slashed:
Ultimately the change won't affect any functionality and everything will work as intended like before, on the other hand the slashing events will be more recognisable.