The address generation mechanism in GenerateAddress
is vulnerable to address colision
To determine an address, we execute the following line address(uint160(uint256(keccak256(abi.encode(_id, "maker")))));
. I'd like to bring our attention to the following piece of code used in here.
`address(uint160(uint256(...)))`
We can notice that, we're casting a uint256 to uint160. This can lead to silent overflows which can result in 2 ids having
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.