Set the Governance hotfix execution window to 24 hours

Governance
1

Context

With CGP-0175 the Security Council became the hotfix co-approver on Celo L2. The hotfix flow is: the approver multisig and the Security Council both call approveHotfix, anyone calls prepareHotfix, and anyone calls executeHotfix within the execution window that starts at prepare time.

Proposal

Set hotfixExecutionTimeWindow on the Governance contract to 86,400 seconds (24 hours). The window is currently 0, which leaves no time between preparing a hotfix and executing it. A day makes sure an approved and prepared hotfix can be executed, with room for coordination, without letting a prepared payload linger.

  • Destination: Governance (0xD533Ca259b330c7A88f74E000a3FaEa2d63B7972)
  • Data: setHotfixExecutionTimeWindow(86400)
  • Value: 0

Why 24 hours

Approvals are collected before prepare, and execution is allowed immediately after prepare, so the window only has to cover the time between those two steps. A day is enough for the approvers and executors to coordinate, and short enough that an unexecuted hotfix expires quickly; once it lapses, anyone can reset the record and both approvals must be given again. It is also the value used throughout the Governance contract’s test suite. Nothing changes about who can approve a hotfix.

5 Likes