Terminology:

• Live: has been recorded as live during the last 14 weeks
• Not-live: has not been recorded as live for more than 14 weeks

1/ Summary

Liveness Expiration Monitoring ensure owners of the Security Council Safe are always showing proof of liveness. For example, if a Safe Owner didn’t show any proof of activity for a “long period” (98 days for now on mainnet) we will have to remove this owner by security measures.

To detect this, we have multiples level of alerting:

1. 14 days before the deadline is met: Safe Owner liveness will expire in 14 days
2. 7 days before the deadline: Safe Owner liveness will expire in 7 days
3. 1 days before the deadline: Safe Owner liveness will expire in 1 day
4. -1 days (deadline is passed): ? (improving in the future).

The alerting is based on the following invariant from the L1 contracts:

• LivenessModule
• LivenessGuard
• SecurityCouncil (GnosisSafe)

(block.timestamp + (`14 days` or `7 days` or `1 day`) > lastLive(owner) + livenessInterval)

2/ Alerts

The priority of this alert is represented by the Priority from the alert emitted by ops-genie.

If the alerted emitted by ops-genie is P2 example below: