When owner of SystemConfig
or TokenManager
manages to execute onlyOwner funciton, he is going to face OwnableUnauthorizedAccount revert, due to owner rights belongs to TadleFactory
, but not to him
As we know, the contracts from SystemConfig.sol
and TokenManager.sol
are going to be deployed as logic contracts and the main contracts for users and owner interactions will be proxies deployed by TadleFactory
. However as we can see from Rescuable
ownable logic, which is inherited by SystemConfig
and TokenManager
, the ownership of the deployed contracts goes to the deployer. So the owner of the logic contracts will be the deployer and the owner of the proxies will be TadleFactory
, which is not expected based on the missing logic in TadleFactory
to interact with any of the proxies.
Core functionality broke, DoS for all functions with onlyOwner modifier
Manual review
Aside from `Rescuable.sol` being OOS, this is invalid based on codehawks guidelines regarding unprotected initializers. Additionally, this should be called concurrently when deploying a new proxy, but this submissions does not identify that particular issue of an uninitialized owner for proxy contracts
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.