Pause > 7 consecutive days
A operational history factor in the v1.7.0 rubric. Measured per protocol on a e cadence.
Methodology how we score #
**What this measures** This factor is a Boolean flag set to true if the protocol has been paused for more than seven consecutive days at least once in the trailing twelve months. It is derived from on-chain pause-event data and updated on each new pause event. A sustained pause -- as distinct from a brief precautionary halt -- indicates either a serious unresolved vulnerability, a governance deadlock preventing the protocol from resuming, or operational instability severe enough to warrant extended downtime.
**Why it matters** A pause lasting more than seven days is qualitatively different from a brief emergency halt. It signals that the underlying issue was complex enough (or the team's response capacity was insufficient) to prevent rapid resolution. For depositors, a seven-day pause means their capital is locked for a minimum of a week with no certainty of when function resumes. In the dataset, extended pauses have preceded both successful recoveries (e.g., multi-week pauses following white-hat negotiations) and protocol sunsettings (e.g., Raft sunsetted after its exploited state made resumption impossible). Either outcome represents material depositor risk.
**Green / Yellow / Red** Green: no pause exceeding seven consecutive days in the trailing twelve months. Yellow: one pause between seven and thirty days in the trailing twelve months, with documented resolution and protocol resumption. Red: any pause exceeding thirty consecutive days in the trailing twelve months, or a pause still active at time of assessment.
**Common gray cases** Planned maintenance pauses announced well in advance (e.g., a scheduled chain migration) may be treated differently from emergency pauses. Curator must verify whether the pause was planned or reactive, and whether user funds were accessible during the pause period.
**Notable historical examples** No cross-hacked incidents currently linked in database for this factor.
Measurement what to look for #
Determine whether the protocol has been paused for more than 7 consecutive days at any point in the last 12 months.