Guardian/pause-keeper distinct from upgrader
Usual (USD0 / bUSD0 / USUAL)'s assessment for RD-F-034 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Multiple pause roles exist (PAUSING_CONTRACTS_ROLE, per-contract pause). Whether these are assigned to addresses distinct from the ProxyAdmin Safe is unconfirmed — RegistryAccess DEFAULT_ADMIN is the same Safe (0xaaDa24...) that controls upgrades. Role separation at contract level exists; at admin level, collapses to one Safe.
Sources #
- EtherscanRegistryAccess — admin is ProxyAdmin SafeRegistryAccess 0x0D374775... initial owner = 0xaaDa24... (same Safe as ProxyAdmin) — single point of role-grant controlretrieved 2026-05-17
- USD0 tech docs — role definitionsUSD0 tech docs: PAUSING_CONTRACTS_ROLE distinct from USD0_MINT role. bUSD0 tech docs: PAUSING_CONTRACTS_ROLE listed separately from other roles.retrieved 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 usual factor RD-F-034 score yellow collected_at 2026-05-16 20:39:44