★ Single admin EOA
Liquity V1 + V2 (LUSD / BOLD)'s assessment for RD-F-027 — scored not_applicable on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
No single admin EOA controls v1 or v2 core contracts. Immutable by design — no admin key exists. v2 Governance owner is renounced post initial-initiative registration via _renounceOwnership(). v2 BoldToken owner renounced post-setup. v1 deployer (0xa850535) has no ongoing authority over any v1 contract.
Sources #
- GitHubBoldToken.sol — Liquity bold GitHubBoldToken.sol setCollateralRegistry() calls _renounceOwnership() — owner permanently revoked post-setupretrieved 2026-05-16
- Liquity v1 FAQ — GeneralLiquity v1 FAQ: 'Liquity has no admin key, and nobody can alter the rules of the system in any way.'retrieved 2026-05-16
Methodology #
Determine whether the effective upgrade/owner/rescue role is held by a single EOA (not a multisig) with no timelock on sensitive operations.
See the full factor methodology and distribution across all protocols →
rubric_version v1.7.0 protocol liquity factor RD-F-027 score not_applicable collected_at 2026-05-16 10:35:50