Proposal execution delay < 24h
Liquid Collective (LsETH)'s assessment for RD-F-038 — scored red on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Zero execution delay on all governance actions. No proposal queuing, no timelock, no minimum delay between signature collection and execution. The three Safes execute transactions immediately. This is confirmed by data cache (timelock_delay_seconds: null) and on-chain structure — TUPProxy and River contracts accept admin calls with no delay check.
Sources #
- GitHubTUPProxy.sol — upgradeTo callable without delay by adminliquid-collective/liquid-collective-protocol/blob/main/contracts/src/TUPProxy.sol — no delay in upgrade pathretrieved 2026-05-17
- Data cache — zero execution delay confirmed.research/protocols/liquid-collective/00-data-cache.json §sources.governance.timelock_delay_seconds=nullretrieved 2026-05-16
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 →
rubric_version v1.7.0 protocol liquid-collective factor RD-F-038 score red collected_at 2026-05-16 19:46:23