The LikeRegistry
contract does have any means to keep track of MultiSigWallet
deployed in the LikeRegistry::matchRewards
function
Users have no direct way to find their MultiSigWallet address after it's deployed. Without emitting an event with the new wallet's address or storing it somewhere, users won't know where their funds went
Severe disruption of the protocol's functionality as users won't be able to access funds sent to the MultiSigWallet
Manual review
Add a means to track deployed MultiSigWallets like a mapping and a event emission whenever a MultiSigWallet is created
Please read the CodeHawks documentation to know which submissions are valid. If you disagree, provide a coded PoC and explain the real likelyhood and the detailed impact on the mainnet without any supposition (if, it could, etc) to prove your point.
The contest is live. Earn rewards by submitting a finding.
This is your time to appeal against judgements on your submissions.
Appeals are being carefully reviewed by our judges.