Missing events for important state changes
Several state-changing functions on Strategy and VaultV3 do not emit events, leaving indexers, dashboards, and on-chain monitoring without a record of when admin actions occurred or who triggered them.
Description
The following calls lack events emitted even though they change important states inside the contracts:
Strategy::claimStrategy::setFrozenStrategy::setSelectorVaultV3::emergencyFreeze
Without events, off-chain consumers (indexers, monitoring tools, dashboards, automated alerting) have no efficient way to detect when these actions are taken or to attribute them to a specific actor and transaction. This degrades both transparency and incident response capability.
Recommendation
Consider adding events to be emitted in the above calls. This provides a clear on-chain record of when and by whom the strategy was claimed, frozen, or had its selector mapping changed, improving transparency and auditability.
Resolution
D2: Ignored "Missing events for important state changes" as we will remove those calls shortly.
Cyfrin: Acknowledged.