Liquid Collective was designed by custodians and exchanges for clients who cannot use an anonymous protocol. Everything about it reflects that: operators are named institutions meeting published standards, the protocol carries slashing coverage arrangements, and disclosure is written for compliance functions.
What institutional design changes
Operators are known entities with contractual obligations rather than pseudonymous participants. Slashing coverage is arranged for holders. Reporting supports audit requirements. For an institution, these features are prerequisites rather than luxuries, and few other LSTs offer them.
The permissioning trade-off
Access is screened, which means LsETH is not a permissionless instrument. That is a coherent choice for the target client and it removes the property that makes liquid staking tokens interesting to everyone else. It also limits DeFi integration, since protocols cannot assume holders are unrestricted.
Liquidity
Thin in open markets by comparison with stETH, reflecting a user base that mostly holds rather than trades. Exiting size generally means the redemption path.
Who should use it
Regulated institutions and their custodians. Individual DeFi users get nothing from the permissioning and give up liquidity, so stETH or rETH are better choices.