registerCollateralToken) and in batches (batchRegisterCollateralToken). However, it lacks a function to deregister or remove collateral tokens, which can lead to security risks, compatibility issues, and reduced flexibility in protocol upgrades.Incompatible Tokens – If a token turns out to be non-functional or incompatible, it cannot be removed.
Security Vulnerabilities – If a token is later found to be exploitable, the contract has no mechanism to prevent its use.
Protocol Upgrades – If an upgrade requires transitioning to a new token, the old one cannot be deactivated.
Manual review
This is invalid. If the collateral token is not supported by Aave or invalid, the `registerCollateralToken` will revert. If the collateral token is deprecated by Aave due to a given issue, this is known issue: "Integration risk with both Aave V3 and DIVA Protocol - vulnerabilities in either protocol may affect AaveDIVAWrapper."
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.