I'm completely aware that the deployment scripts are not in scope but hear me out:
I don't know if the same deployment script is going to be used when this codebase gets deployed to mainnet or just add other things to it while not bothering to check the address, either way is gonna cause an issue (if you/ protocol team think that its the case then give me this high severity issue, come on). Enough chit chat lets get into it.
Nothing much, the contract address of jpycv2
is wrong in the HelperConfig: :getPolygonConfig()
of HelperConfig.sol.
The given contract address can be viewed in polygonscan here.
Since wrong token address is used, it can lead to tokens being send to non-desirable contract and can cause lockup of funds and also breaking the system in cases where it uses jpyc v2.
Manual review
Just add the correct contract address for the token and you are good to go, and oh you might want to uncomment the contract address for usdt which is the correct contract address. Even though its not used in tests, the array slot return zero address now ig??.
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.