Optimistic governance

Rather than asking the community to vote yes until quorum is reached, optimistic governance assumes the yes and only requires action to stop the proposal. The core piece is the challenge period, a mandatory delay between when a proposal is queued and its on-chain execution, typically ranging from 24 hours to 7 days. During that window, an entity with veto power can challenge it. In OpenZeppelin or Tally implementations there is a veto Governor whose voting period must be shorter than the timelock delay so it can cancel in time, and the veto usually needs a rejection quorum rather than a majority in favor. It is not a formal EIP but a Governor plus Timelock contract pattern, settled in practice since 2022.

It cuts operational friction. It spares every minor decision from having to beat quorum, the chronic bottleneck of low-participation DAOs, and speeds up execution while keeping a safety brake. It is applied selectively, well suited to maintenance upgrades, technical changes or routine parameter tweaks that need oversight but not extensive deliberation. The trade-off is clear: if nobody watches during the veto window, a faulty proposal passes by default, so the model depends on attentive delegates or guardians and a sufficiently long challenge period.

The Optimism Collective uses optimistic approval across many of its decision modules: the Token House approves protocol upgrades subject to a Citizens' House veto, with a one-week veto period and a 30% threshold for it to take effect, per its documented design and subject to per-season iteration. Aave applies a mandatory timelock before implementing proposals, with different windows depending on the scope of the change, and its Aave Guardian can cancel faulty ones. Aragon OSx ships an optimistic dual-governance plugin as a reference design.