LUSD: who controls it?

The control finding

Liquity. Immutable contracts, no governance, no admin key, no blocklist — the most censorship-resistant stablecoin that exists. But supply has contracted from a ~$1.5B peak to roughly $30M, so it is not usable at client size. Sovereignty and availability are separate questions, and this is the clearest case where they diverge.

Named controller

None. Immutable contracts, no admin key, no governance.

Holder’s position

LUSD is minted against ETH collateral locked in immutable Liquity vaults, called Troves. The holder's claim depends on the fixed liquidation mechanics coded into the protocol, not on any party's discretion.

Redemption or exit

Any LUSD holder can redeem directly against the protocol's ETH collateral at face value, a right written into the immutable contracts. No issuer or intermediary can block it.

Dependencies an advisor should record

• The immutable Liquity contract set
• Collateral quality and the fixed liquidation mechanics
• On-chain liquidity, which has thinned considerably
• The chain carrying the position

Why this distinction matters

Sovereignty and availability are separate questions, and LUSD is the clearest case where they diverge. Supply has contracted from a roughly $1.5 billion peak to about $30 million, so a position of meaningful size may not be executable even though the contract itself is beyond reach. Record both facts in the file, not just the first one.

No single issuer or administrator has an address-level freeze function at this layer. That finding can coexist with a sound reserve, useful product, or appropriate client role. The grade prevents the on-chain wrapper from being mistaken for the absence of an administrator.

Questions before use

1. Does the exact contract and chain match the instrument reviewed here?
2. Which party can mint, burn, pause, upgrade, block, or redeem?
3. Does the client have direct redemption access or only secondary liquidity?
4. What protocol, bridge, wallet, and custodian dependencies are added?
5. Which event would force review or exit?