The RAACNFT contract has vulnerabilities related to immutable dependencies, price oracle integration, and token. The contract permanently binds critical external contract addresses at deployment with no update mechanism, potentially requiring redeployment if issues arise with dependent contracts.
Contract must be redeployed if token or oracle contracts need updating
Users could lose access to NFT functionality if dependent contracts fail
No emergency mechanisms for critical contract updates
Potential loss of funds if token contract becomes compromised
Service disruption if oracle needs upgrading
Add update mechanisms for dependencies:
Manual code review
Foundry testing framework
Static analysis
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.