When setPoolScope() is the first function to observe the registry moving past pre-attack staging, _observePoolState() sets scopeLocked = true and emits ScopeLocked. However, the immediately following if (scopeLocked) revert ScopePostLockImmutable() reverts the entire transaction, rolling back both the state change and the event. The scope is functionally immutable but scopeLocked stays false on-chain and no ScopeLocked event is recorded until another function commits _observePoolState().
State write and event are inside the same transaction that reverts -> both disappear.
setPoolScope() never execute on that case. The state not handled appropriately there. Persists until another function (stake, withdraw, pokeRiskWindow) commits _observePoolState().
Check scope lock before observing, then re-check after:
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.
The contest is complete and the rewards are being distributed.