The ScrvusdVerifierV1
and ScrvusdVerifierV2
contracts set the oracle address as immutable during construction, preventing any updates to the oracle if it becomes compromised, deprecated, or requires an upgrade. This design creates a rigid dependency that could force a complete redeployment of the verification system if oracle issues arise.
In both verifier contracts, the oracle address is set as an immutable state variable:
The verifier contracts rely on this oracle to update price information:
Once deployed, there's no mechanism to change this address if needed.
The immutable oracle design forces complete system redeployment if the oracle requires replacement, causing service disruptions
Manual review
Add admin/owner function to update the Oracle address
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.