The parameter is named tswapAddress, which suggests it is the address of a specific TSwap pool rather than the factory that manages all pools. OracleUpgradeable.__Oracle_init() correctly names the same value poolFactoryAddress, creating an inconsistency across the call chain.
Likelihood:
Any developer initialising the contract without reading OracleUpgradeable internals is likely to pass the wrong address type
Deployment scripts that auto-populate tswapAddress from config may point to a pool rather than the factory
Impact:
Silent misconfiguration — no revert, fees silently become zero for all tokens
Requires full redeployment to correct if caught late
Rename the parameter to match OracleUpgradeable:
The contest is live. Earn rewards by submitting a finding.
Submissions are being reviewed by our AI judge. Results will be available in a few minutes.
View all submissionsThe contest is complete and the rewards are being distributed.