The current _handleTokenOperations
hardcodes the referralCode parameter to 0
in the Aave V3 supply()
function.
While the referral system is currently inactive, Aave's documentation indicates that it may be activated in the future through a governance proposal. By hardcoding referralCode to 0, the integration fails to account for the possibility of future referral rewards.
One of the core features of the AaveDIVAWrapper
is the yield generated while the collateral sits idle, which users would benefit from. A hardcoded value would result in users missing out on potential incentives for referring others to the protocol and any missed opportunity for users to maximize their earnings (including potential referral rewards) undermines overall value proposition which is essentially a core goal and promise to users.
Consider allowing users to specify a referral code once the referral system is active.
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.