INF: who controls it?

The control finding

Sanctum Infinity. A basket of Solana LSTs — you inherit the weakest constituent rather than choosing the strongest.

Named controller

No token freeze authority; composition governed by the Sanctum Infinity pool

Holder’s position

INF represents a pro-rata claim on a basket of underlying Solana LSTs held by the Sanctum pool. It is not a claim on a single validator, company, or reserve.

Redemption or exit

Holders redeem INF through Sanctum for a basket-weighted mix of underlying LSTs, subject to each constituent's own unstake queue and epoch timing, or sell INF on the open market.

Dependencies an advisor should record

• Sanctum pool program and its upgrade authority
• Composition and rebalancing rules across constituent LSTs
• Weakest-constituent delegation and exit risk
• Epoch-timed unstake queues on the underlying LSTs
• Market liquidity for instant exit

Why this distinction matters

A basket token trades single-validator risk for composition risk. A fiduciary should treat INF's grade as a statement about its weakest constituent, not an average, and record which LSTs currently sit in the basket before relying on it.

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?