The MultiSig wallet created during mutual matches is not tracked, and no event is emitted.
The LikeRegistry::matchRewards
function deploys a new MultiSig wallet but does not store its address or emit an event. This makes it difficult to track or interact with deployed MultiSig wallets.
Lack of tracking for MultiSig wallets limits transparency and usability.
Users and the contract owner cannot easily monitor or interact with deployed wallets.
Potential loss of funds if users cannot track where their funds are being transferred to
Manual code review.
Add a mapping or array to track deployed MultiSig wallets or emit an event. With this resolution, we will emit an event.
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.
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.