There is no explicit mechanism to ensure that the same proof cannot be replayed or that proofs are processed in order. Contract ScrusdVerifierV1
If an attacker is able to resubmit an old but valid proof, it might affect the pricing update
an attacker could repeatedly trigger oracle updates using the same valid proof. This may cause incorrect or manipulated pricing data to be submitted to the oracle, potentially disrupting dependent systems and harming the protocol's integrity.
Manual
Replay Protection: Use a mapping to store processed block numbers and ensure each proof is processed only once.
- All proof generated within `_proof_rlp` is generated via the off-chain prover, so there is no concrete proof that this proofs are non-unique. - All state roots and proofs must be verified by the OOS `StateProofVerifier` inherited as `Verifier`, so there is no proof that manipulating proofs can successfully pass a price update
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.