MUST: who controls it?

The control finding

Mustang MUST is a Liquity V2-style, crypto-collateralized debt token without a conventional issuer blocklist, but a disclosed 2-of-3 governance Safe controls protocol parameters.

Backing

Liquity V2-style overcollateralized crypto borrower positions.

Holder’s position

MUST is protocol debt supported by collateral and liquidation mechanics rather than a reserve issuer’s obligation.

Redemption or exit

Protocol redemption and secondary liquidity provide exit, subject to collateral health, fees, and system parameters.

Dependencies an advisor should record

• 2-of-3 governance Safe
• Collateral and oracle quality
• Liquidation and stability-pool mechanics
• Exact deployed contracts

Material incident check

• No material control, reserve, or redemption incident was identified in the reviewed sources.

Why this distinction matters

Record Mustang governance, including a disclosed 2-of-3 Safe as the controlling party, verify direct-redemption eligibility, and do not treat an on-chain balance as eliminating reserve, custody, contract, or legal dependencies.

On-chain governance or collateral mechanisms matter, but no conventional issuer blocklist defines the asset. 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?