Sanctum Burns Its CLOUD Community Reserve, Cutting Token Supply to 740.7 Million as SANC Ticker Appears

Sanctum CLOUD$0.061+5.9%, the Solana liquid staking protocol, has burned the Community Reserve of its CLOUD token, carrying out the proposal tokenholders approved in September. Sanctum said on 7 October 2026 that the burn "is done" and linked a Solscan transaction that destroyed 250 million CLOUD at 02:43 UTC on 6 October. Total supply now stands at about 740.7 million tokens, down from roughly 1 billion, according to Solscan's token page, which also now displays the token under its new ticker, SANC.

What the 250 million CLOUD burn transaction shows on-chain

The transaction Sanctum linked was finalized in slot 453,770,313 at 02:43:27 UTC on 6 October 2026, according to Solscan. Solscan labels the owner of the burned tokens as Sanctum's "Community Cold Multisig", and the instruction ran through Squads, whose multisig program holds assets in a vault that only moves once the required number of keyholders has approved. It destroyed 250,000,000.07 CLOUD and left the multisig's token account with a balance of zero.

Solana Compass's own daily series for the token records about 999.99 million CLOUD on 5 October and about 740.67 million on 6 October, a fall of roughly 259 million. That matches the size of the reserve in proposal CLOUD-008, which set out to "burn the remaining Community Reserve of 259M CLOUD, roughly ~25% of total supply." The linked transaction accounts for 250 million of the reduction. The other 9.3 million or so is not in it, and Sanctum's post links no second transaction. Sanctum described the burn as "25% of the total supply, permanently removed"; measured against the pre-burn supply in our data, the full reduction works out to about 25.9%.

Sanctum's event page had billed the burn as happening "live on stage at Solana Summit in Singapore" during Sanctum Day, scheduled for 5 PM Singapore time on 6 October. The linked transaction is timestamped 10:43 AM Singapore time, a little over six hours before that slot. Sanctum's completion post does not address the difference.

What a smaller token supply changes for Sanctum holders

The burned tokens had never been distributed, so no holder's balance changed. Sanctum's proposal said the Community Reserve launched with about 307 million CLOUD and that only about 48 million had ever left it, most of it as staking rewards. With the rest destroyed, each remaining token is a larger share of a smaller total. Solana Compass counts roughly 78,000 wallets holding the token on 5, 6 and 7 October alike.

Sanctum's proposal post argued the unused reserve was "a large structural overhang that turns away investors who fear that reserves may get dumped on them", and said burning it "removes the token overhang of the Community Reserve once and for all" while raising existing holders' share of ownership. The 740.7 million figure is total supply, and it still includes tokens Sanctum controls. The proposal's FAQ said the Strategic Reserve, which Sanctum also calls the Team Reserve, would stay intact: "110M was earmarked for the Strategic Reserve, and today the Strategic Reserve stands even above that." Sanctum wrote that it plans to use those tokens for grants and options for founders and staff.

SANC ticker goes live on Solscan with no rename date announced

Solscan now titles the token "Sanctum (SANC)" and labels its trading pools with the SANC ticker, on the same mint address as before. Sanctum's event page also calls the token SANC. CLOUD-008 described the rename as "a simple metadata change of the token name, symbol and logo", with "tokenomics and the token address" unchanged. Sanctum announced the rename in the same post as the burn proposal; the vote itself covered the burn.

Sanctum's burn announcement gives no date for the metadata change, and the new name has not reached every site: Solana Compass's own token page still listed the asset as CLOUD on 7 October. The mint address, CLoUDKc4Ane7HeQcPpE3YHnznRxhMimJ4MyaUqyHFzAu, is the same under either name, which makes it the dependable way to identify the token while tickers differ between trackers.

From the CLOUD-008 vote to execution, and Streamflow's burn two weeks earlier

The burn closes a sequence that took five weeks. Sanctum proposed burning the reserve and renaming the ticker on 2 September, then opened a 72-hour vote on MetaDAO META$5,217.13-3.3%, where a proposal passes or fails according to how traders price the token under each outcome. Sanctum reported that the proposal had passed on 19 September, and the 250 million CLOUD transaction landed 17 days later. In between, Sanctum released version 2.0 of its mobile app.

Sanctum's burn follows a similar deletion of undistributed supply at another Solana project. The Streamflow STREAM$0.00976-0.5% Foundation burned 699.99 million tokens on 23 September, and Solana Compass data shows STREAM supply at about 1 billion on 23 September and about 300 million on 24 September. In Sanctum's case, a market-based tokenholder vote approved the burn before the multisig executed it.