The LikeRegistry
contract deploys a MultiSigWallet
contract for matched users but does not provide a way to recover the address of the deployed MultiSigWallet
. This makes it difficult for users to interact with their multisig wallet without manually tracking the on-chain transactions.
In the matchRewards
function, a new MultiSigWallet
contract is deployed for the matched users. However, the address of this newly deployed contract is not stored or made accessible through the LikeRegistry
contract. This oversight forces users to manually track the on-chain transactions to find their multisig wallet address, which is not user-friendly and can lead to potential issues in accessing their funds.
User Inconvenience: Users have to manually track the on-chain transactions to find their multisig wallet address, which is not user-friendly.
Potential Loss of Funds: If users are unable to find their multisig wallet address, they may lose access to their funds.
Operational Complexity: Increases the complexity of interacting with the LikeRegistry
contract and the deployed MultiSigWallet
contracts.
Manual code review
Implement a mapping in the LikeRegistry
contract to store the addresses of the deployed MultiSigWallet
contracts. This will allow users to easily retrieve their multisig wallet address.
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.