Proposal execution delay < 24h
Jupiter Perpetual Exchange'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 #
Squads v4 time_lock_seconds=86400 (exactly 24 hours) confirmed on-chain from multisig config AxkJ8oH5... Program upgrades through the Squads v4 multisig have a 24-hour delay. This is at the lower acceptable threshold (not <24h, which would be red; not >24h, which would be green). Prior red (assumed no timelock / Squads v3) corrected by on-chain derivation. DAO governance when active has no confirmed additional execution delay. Direct admin instruction paths (if any in closed-source program) may have no delay. Scored yellow: 24h timelock confirmed and real; borderline adequate for $691M TVL.
Sources #
- TxSquads v4 multisig config AxkJ8oH5 on SolscanOn-chain borsh decode of Squads v4 multisig config AxkJ8oH5aDu4ZRWfsujPtxdb6Vhq4gDehpoReBgrUUSm: time_lock=86400 seconds (u32 LE bytes 74-78 per SOLANA_GOVERNANCE.md Step4 Squads v4 layout)retrieved 2026-05-16
- SOLANA_GOVERNANCE.md Squads v4 Multisig layoutSOLANA_GOVERNANCE.md Step4 Squads v4 layout: time_lock at bytes 74-78; 86400s = 24h exactly at the boundary of the RD-F-038 24h thresholdretrieved 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 →