UniswapV3 Router swaps do not support Fee-On-Transfer tokens whilst `PAXG` is supported by the system
Vulnerability Details
As per official documentation by Uniswap (https://docs.uniswap.org/concepts/protocol/integration-issues)
Fee-on-transfer and rebasing tokens will not function correctly on v3.
Fee-on-transfer tokens will not function with our router contracts. As a workaround, the token creators may create a token wrapper or a customized router. We will not be making a router that supports fee-on-transfer tokens in the future.
The protocol supports PAXG as a swappable token in SmartVaultV3.sol#swap() but has no custom logic to accommodate for a fee-on-transfer token so any swaps with PAXG as tokenIn will fail.
Impact
PAXG is supported but cannot be swapped when it's supposed to be able to be.
Tools Used
Manual Review
Recommendations
Follow UniswapV3 Recommendations in documentation page I provided.
Lead Judging Commences
fee-on-transfer
Prize pool breakdown
Live
The contest is live. Earn rewards by submitting a finding.
Appeals
This is your time to appeal against judgements on your submissions.
Appeals Review
Appeals are being carefully reviewed by our judges.