The burn function in the RAACToken contract incorrectly transfers tax amounts to the feeCollector contract using the _transfer function instead of the collectFee function. This prevents the correct distribution of fees, as the feeCollector contract is designed to only process fees collected through the collectFee function.
The RAACToken contract's burn function has the issues:
The function utilizes _transfer to send the calculated tax amount to the feeCollector instead of using the collectFee function. This bypasses the necessary fee-collecting mechanism implemented in the feeCollector.
Since the feeCollector is designed to distribute fees only when invoked through the collectFee function, using _transfer results in fees not being recorded properly. Consequently, these fees will not be correctly allocated or trigger any associated distribution logic.
This vulnerability can lead to untracked fees, which can impact the operational efficiency and transparency of the fee distribution process. Failure to account for collected fees means that various financial calculations based on these fees might be incorrect, leading to potential losses and affecting user trust in the contract’s reliability.
Modify the burn Function: Ensure that the tax amount is sent to the feeCollector using the collectFee function instead of using _transfer
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.