★ delegatecall/call in proposal execution without allowlist

Across Protocol's assessment for RD-F-039 — scored gray on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.

Evidence summary #

`delegatecall`/`call` in proposal execution, no allowlist | oSnap (via Gnosis Safe module) submits Safe transactions — these are CALL operations, not arbitrary DELEGATECALL to proposal-supplied targets. Safe's Module execution standard uses standard CALL. However: (a) there is no documented target allowlist for oSnap-executed transactions; (b) contract exclusions ("select contract exclusions to prevent protocol upgrades") were announced at launch but current status of those exclusions is undo...

Sources #

Curator note
Extracted from 02-governance-admin.md — RD-F-039; no URL citedretrieved 2026-04-28

Methodology #

Determine whether the governance executor contract uses `delegatecall` or `call` with proposal-supplied target, without enforcing an allowlist of permitted targets.

See the full factor methodology and distribution across all protocols →

rubric_version v1.7.0 protocol across-protocol factor RD-F-039 score gray collected_at 2026-04-30 21:19:18