Proposal execution delay < 24h
Usual (USD0 / bUSD0 / USUAL)'s assessment for RD-F-038 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
No on-chain governor or proposal execution queue. MultIsig executes immediately after reaching threshold — effectively 0h delay between decision and execution. Factor targets on-chain governor delay specifically; off-chain Snapshot + immediate multisig execution is a structural gap that doesn't fit the green/red definition exactly. Assessed yellow as structural concern without on-chain queuing.
Sources #
- GovernanceRevenue Switch blog — activation timeline shows no queuingUsual blog Jan 7, 2025: Revenue Switch activated Jan 13 — 6-day window from announcement to activation, no on-chain queueretrieved 2026-05-17
- Usual data cache — no governor, no delay00-data-cache.json: governance.governor_address = null; governance.timelock_delay_seconds = nullretrieved 2026-05-17
Methodology #
Determine whether the time between a governance proposal passing and its executability (including any internal delay) is less than 24 hours.
See the full factor methodology and distribution across all protocols →