Sanctum is a Solana protocol that builds routing and shared liquidity for liquid staking tokens (LSTs). Its SANC token was previously called CLOUD; Sanctum’s official proposal says the ticker change was a metadata update and the token address remained the same. SANC is distinct from INF, the liquidity-provider token used by Sanctum’s Infinity pool.
| Protocol documentation | Documentation |
|---|---|
| Chart | CoinGecko Chart |
| Directories | Solana Directory |
| Stat | Value |
|---|---|
| Ticker | SANC (formerly CLOUD) |
| Price | $0.05076 |
| Market cap | $25.155M |
| 24-hour change | +4.0% |
| Circulating supply (CoinGecko) | 495.57 million SANC |
| Total supply (Sanctum dashboard) | 740,669,457 SANC |
| Maximum supply | 1 billion SANC |
| Network | Solana |
| Contract | CLoUDKc4Ane7HeQcPpE3YHnznRxhMimJ4MyaUqyHFzAu |
CoinGecko market-data snapshot checked 2026-10-24. CoinGecko and Sanctum report different circulating-supply figures; the table labels each provider’s value.
In-Depth Explanation
Sanctum provides infrastructure for moving among supported Solana LSTs and SOL. Infinity is a shared liquidity pool: users can swap supported LSTs and SOL or deposit them to receive INF, which represents a share of the pool. Fees apply, and available liquidity depends on the pool’s assets and operation. Infinity is separate from the Sanctum Reserve, which the documentation describes as last-resort backstop liquidity rather than a retail deposit pool.
Tokenomics
The token’s former CLOUD ticker changed to SANC without creating a separate mint. The maximum supply is 1 billion. Sanctum’s investor dashboard says 259,321,838 SANC from the Community Reserve was permanently burned on 2026-10-06 and reports total supply of 740,669,457 SANC. As of the CoinGecko snapshot above, CoinGecko reports 495.57 million circulating; Sanctum’s dashboard reports 530,071,870. These provider-reported circulating figures differ, so they should not be treated as a single reconciled number.
History
Sanctum’s 2026 governance proposal discussed a Community Reserve burn and announced a metadata-only ticker change from CLOUD to SANC. MetaDAO lists the burn decision as passed; the investor dashboard records the later burn. Sanctum’s technical documentation describes Infinity and Reserve as separate products with different liquidity roles.
Social Media Sentiment
In one English-language Sanctum Research forum thread about the 2026 reserve-burn proposal, commenters expressed mixed views. Some supported reducing the unused reserve and making the token easier to associate with Sanctum; others questioned SANC’s future utility, the loss of a community-controlled reserve, or whether the burn and ticker change were both part of the vote. The thread is a sample of one proposal discussion, not a measure of all SANC holders or general user satisfaction. The post’s author clarified that only the burn was subject to the decision market; the ticker update was a separate metadata change.
Last updated: 2026-10-24
Related Terms
See Also
- Is Ethereum Staking Making the Network More Centralized?
- What Is Restaking — And Why EigenLayer Made It the Most Debated Idea in DeFi
- Why DAO Governance Votes Often Fall Short — and Why Protocols Still Use Them
Swap crypto with ChangeNOW.
Sources
- Sanctum Docs, “Infinity – Technical” — explains the shared LST liquidity pool, INF deposits, and fee mechanics.
- Sanctum Docs, “Sanctum Reserve” — describes the Reserve’s last-resort backstop role and retail-deposit status.
- Sanctum Research, “CLOUD-008: Should Sanctum burn 1/4 of total CLOUD supply?” — official proposal explaining the planned reserve burn and metadata-only ticker change.
- MetaDAO, Decisions — records the Sanctum reserve-burn decision as passed.
- Sanctum Investor Relations — reports the 2026-10-06 burn, current total supply, and the dashboard’s circulating-supply figure.
- CoinGecko, Sanctum (SANC) — current listing and the dated market-data snapshot.