# Governance: Rotation Delay **URL:** https://forum.hypercore.one/t/governance-rotation-delay/938 **Category:** General **Created:** [July 6, 2026, 12:21am UTC](https://forum.hypercore.one/t/governance-rotation-delay/938 "2026-07-06T00:21:05Z") **Posts on this page:** 1 **Page:** 1
### Author: ![Stark](https://forum.hypercore.one/user_avatar/forum.hypercore.one/stark/32/656_2.png) [@Stark](https://forum.hypercore.one/u/Stark) #### Post date: [July 6, 2026, 12:21am UTC](https://forum.hypercore.one/t/governance-rotation-delay/938/1 "2026-07-06T00:21:05Z")
Sharing ai summary for clarity/discussion. The 72-hour execution delay applies only after approval in a ratchet round. It does not form part of the voting periods. The lowest participation threshold first becomes available only after the earlier rounds have fully elapsed without a decision. Clear Timeline to the Absolute Minimum Threshold (Round 2) A Type-2 proposal (signer rotation) begins in Round 0 with the strictest thresholds: - Round 0 Active-Pillar threshold: \>50% Directional threshold: \>50% Period: 30 days If the proposal remains undecided at the end of these 30 days (neither approval nor rejection thresholds are met), it automatically ratchets to Round 1. A fresh vote tally begins under new parameters. - Round 1 Active-Pillar threshold: \>40% Directional threshold: \>60% Period: 14 days If this round also ends undecided, the proposal ratchets again. At this moment — the end of Round 1 — the proposal enters Round 2, where the absolute minimum participation threshold first applies: - Round 2 (lowest threshold) Active-Pillar threshold: \>33% floor Directional threshold: \>66% Period: 14 days Time required to reach the start of Round 2 (i.e., the first moment the absolute minimum threshold of \>33% becomes available): 30 days + 14 days = 44 days from the original proposal submission. Relation to the 72-Hour Execution Delay Only once the proposal is in Round 2 can it be approved under the lowest threshold. Approval may occur at any time during Round 2 as soon as the yes/no conditions are satisfied (it does not have to wait until the end of the 14-day period). Upon approval in Round 2, the 72-hour execution delay immediately begins. The new signer set cannot be executed until ApprovalTimestamp + 72 hours. Therefore, in the scenario you describe — reaching the absolute minimum threshold regime for the first time — the earliest point at which a low-turnout rotation could become executable is: - 44 days (to enter Round 2) - - time required to meet the Round-2 thresholds (which could be short once voting begins) - - 72 hours execution delay The 72-hour delay sits strictly after approval and after whatever ratcheting was necessary to reach that round. It is the final safeguard specifically for ratchet-round approvals, ensuring the pending rotation remains visible on-chain for contestation before it lands.