Sanctum SANC burn cuts a quarter while Solana unlocks
Sanctum SANC burn is set for 259 million tokens after a Sept 19 vote. CryptoBriefing says Oct 6. SolanaFloor says Oct 9.
Early story. Some claims here are not officially confirmed yet. We update this post as it confirms.
- CryptoBriefing's October 1 unlock roundup and SolanaFloor's October unlock guide both put the burn at 259 million tokens and a post-burn total near 741 million.
- CryptoBriefing dates the burn to October 6. SolanaFloor dates the burn to October 9. This article does not pick a winner.
- Both tie the decision to a September 19, 2026 governance vote, not to a silent team burn.
in this block
Sanctum SANC burn is the odd entry on October's Solana supply calendar: while DoubleZero, TRUMP, PUMP, and deBridge are scheduled to unlock tokens, Sanctum is scheduled to destroy a quarter of its supply after a September governance vote. Two October roundups agree on the size. They do not agree on the day.
What actually happened
Sanctum SANC burn coverage sits inside broader Solana unlock stories, not as a standalone press release in the tabs opened for this draft. CryptoBriefing says token holders approved the burn on September 19, 2026, that 259 million SANC will be destroyed, and that total supply should fall to approximately 741 million. SolanaFloor repeats the 259 million figure and the drop from about 1 billion to 741 million. The shared arithmetic is the part that matters. The calendar day is not shared.
Ticker history is SolanaFloor's extra lane. That guide says Sanctum changed the ticker from CLOUD to SANC in September while keeping the token address and tokenomics unchanged. CryptoBriefing's opened unlock story uses SANC without reprinting the CLOUD rename. Keep the rename attributed to SolanaFloor. Do not invent a contract migration that neither page describes.
SolanaFloor also lists 10.80 million SANC of linear vesting in October, worth about $778,000 on its page. CryptoBriefing's opened story does not center that vesting line. The burn and the vesting are different supply events. This piece does not merge them into one "Sanctum October" blob.
Why the date split stays on the page
When two roundups disagree by three days, the honest move is to show both stamps. CryptoBriefing says October 6. SolanaFloor says October 9. A reader setting a calendar alert should open both pages again near the date, or the Sanctum research forum those roundups imply, rather than trust a blended "early October" fog. memcool does not average October 6 and October 9 into October 7.5.
The purpose language is cleaner. CryptoBriefing says the burn aims to remove excess supply in an underused community reserve. SolanaFloor frames it as a major supply reduction on a month otherwise dominated by unlocks. Neither page promises a price floor. A supply cut without a demand story is still just a supply cut.
How it sits next to the unlock list
CryptoBriefing's same article leads with DoubleZero's cliff, then Official Trump, Pump.fun, and deBridge, before the Sanctum reversal. SolanaFloor's guide does the same ordering by size and then calls out Sanctum separately. Readers who want the DoubleZero numbers with their own source conflict can open the DoubleZero unlock note. Readers watching memecoin index churn can open the memecoin index rebalance note. Neither replaces the Sanctum SANC burn vote.
Primary links for this draft are CryptoBriefing's Solana unlocks roundup and SolanaFloor's October unlock guide. If you cite the burn size, cite 259 million and ~741 million after. If you cite the day, cite both desks.
Community reserve versus circulating float
CryptoBriefing's purpose line — cleaning an underused community reserve — matters because a reserve burn is not automatically a float burn. If a wallet's liquid float does not change on burn day, traders who priced a squeeze off total-supply headlines will be reading the wrong column. Sanctum SANC burn is still a real governance event. It is not a magic circulating-supply disappearing act unless an official post says the burned tranche was circulating.
The rename from CLOUD to SANC is another place people get sloppy. SolanaFloor says the address stayed put. A phishing token with a fresh mint and a SANC ticker would not be the same asset. Always match the address your wallet already trusts, not the three letters on a timeline screenshot.
What to do as a reader
Treat this topic as a governance-approved supply cut with a disputed execution day across secondary roundups. Check the Sanctum forum or an official channel before you mark a calendar. Do not trade a narrative that "all of Solana is unlocking" without noticing this opposite print. Nothing here is a buy or sell call on SANC. Not financial advice. DYOR, ser.
For adjacent memcool context, see also clef decision models and cashcat listing.
Not financial advice. DYOR, ser.
