Proposal execution delay < 24h

Meteora'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 #

Squads v3 executes program upgrades immediately after threshold approval — on-chain execution delay is 0 hours. No proposal queue or delay mechanism. This is a structural Squads v3 property (no time_lock field). All admin actions (upgrade, config, pool disable) execute with 0-hour delay once multisig threshold is met.

Sources #

Internal
Solana Governance Verification MethodologySOLANA_GOVERNANCE.md — Squads v3 borsh layout has no time_lock field; execution is immediate after thresholdretrieved 2026-05-16
Docs
Squads Protocol v4 GitHubSquads Protocol v4 overview — v3 vs v4 feature difference: time_lock added in v4 onlyretrieved 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 meteora factor RD-F-038 score red collected_at 2026-05-16 10:03:05