★ delegatecall/call in proposal execution without allowlist

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

Evidence summary #

No governance proposal execution engine. The AllocateModule uses delegatecall internally for strategy routing but is called by the Allocator role (not a public governance proposal path) and operates on pre-approved strategy contracts only. Not the delegatecall-in-proposal-execution pattern this factor measures.

Sources #

GitHub
ConcreteStandardVaultImpl.sol — delegatecall in Allocator role (not proposal execution)ConcreteStandardVaultImpl.sol: allocate() uses AllocateModule delegatecall for strategy routing — this is role-gated (ALLOCATOR) and targets pre-approved strategies, not user-supplied proposal targetsretrieved 2026-05-17

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 concrete factor RD-F-039 score not_applicable collected_at 2026-05-17 14:36:59