Guardian/pause-keeper distinct from upgrader
Concrete's assessment for RD-F-034 — scored red on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
No guardian or pause-keeper role identified. ConcreteFactory has no pause() function. VaultProxy has no pause mechanism. The Allocator role can halt fund routing but is not a protocol-level pause guardian distinct from the upgrader. No separate pause-keeper address found.
Sources #
- GitHubConcreteFactory.sol — no pause/guardian mechanismConcreteFactory.sol: no pause() function; no guardian role; onlyOwner only for admin actionsretrieved 2026-05-17
- ConcreteStandardVaultImpl.sol — no pause guardianConcreteStandardVaultImpl.sol: role-based (VAULT_MANAGER, ALLOCATOR, STRATEGY_MANAGER, HOOK_MANAGER) but none is a pause-keeper distinct from upgraderretrieved 2026-05-17
Methodology #
Determine whether a pauser/guardian role exists and is held by an address distinct from the upgrader address.
See the full factor methodology and distribution across all protocols →
rubric_version v1.7.0 protocol concrete factor RD-F-034 score red collected_at 2026-05-17 14:36:59