Description: The codebase inconsistently uses require
statements and custom errors. In all contracts, require
statements are used instead of custom errors, only MultiSig.sol
contract in some places uses custom errors but without a consistent naming convention.
Found in:
LikeRegistry.sol
:
MultiSig.sol
:
SoulboundProfileNFT.sol
Recommended Mitigation:
Use custom errors instead of require statements:
Follow consistent naming convention ContractName__ErrorName
:
Do the same for the others
Benefits:
Custom errors are more gas efficient
Better error handling and debugging
Consistent naming helps with code maintenance
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.