Sanctum Burned a Quarter of Its Supply. Not One Circulating Token Disappeared.

At 02:43 UTC on October 6, a Squads multisig labeled "Community Cold Multisig" sent Sanctum's entire community reserve to the burn instruction. The transaction took total supply of the Solana liquid-staking protocol's token from about 1 billion to roughly 740.7 million, and the ticker changed from CLOUD to SANC on the way out. Crypto feeds called it a 25% supply cut.

The circulating supply, the tokens anyone could actually buy or sell, stayed exactly where it was. The 259,320,217 destroyed tokens came from a reserve that was never part of circulating supply, which held at about 519.5 million before and after.

A quarter of the supply, gone. Zero tokens off the market.

That isn't a scandal, and Sanctum never claimed otherwise. Its governance documents were explicit about what was and wasn't being burned. But the gap between the headline number and the market number is the most useful lesson in tokenomics this month, because it shows what a burn actually buys.

A Token Burn Is Only as Big as the Discretion It Removes.

The Reserve Was Never Supply Anyone Could Trade.

Start with how the reserve got so large. Sanctum launched its token in July 2024 through Jupiter's LFG launchpad and set aside about 307 million tokens for the community. Only 48 million were ever distributed: 45 million through its Active Staking Rewards program and about 3 million in liquidity incentives. Sanctum shut staking rewards down in August with a final 15 million-token distribution. The remaining 259 million just sat there.

Burning tokens nobody can trade does nothing to the float. What it changes is the denominator. Before the burn, Crypto Briefing put Sanctum's market cap near $12 million against a fully diluted valuation near $24 million, with about half the supply circulating. After it, the circulating share rises to around two-thirds. The valuation metric that screens on fully diluted value looks better overnight, and the order book looks exactly the same.

Sanctum's own stated reason was refreshingly blunt. The proposal said "investor feedback specifically flagged supply concerns as a drag on market prospects." The point was to change what a spreadsheet showed to a prospective buyer, and on those terms it worked.

Unscheduled Tokens Are Scarier Than Scheduled Unlocks.

Here's why the spreadsheet mattered more than it sounds. Compare Sanctum with the other big Solana supply event of the month.

On October 2, DoubleZero's 12-month cliff expired and about 1.78 billion 2Z tokens, worth more than $110 million, began unlocking to early backers including Jump Crypto and Malbec Labs. Crypto Briefing counted it at roughly a third of the circulating float, and AMBCrypto estimated it would lift circulating supply to about 51% of the total. In the same window, Hyperliquid, Ethena and Aptos helped push early-October unlocks past $1.1 billion.

That is real new supply hitting real wallets. And yet DoubleZero's unlock was, in one sense, the less worrying kind. Everyone knew the date and the amount, and roughly who would receive it. Traders could price it months in advance.

Sanctum's reserve had none of those properties. No release schedule, no lockup, no published recipient. It was a pile of tokens under multisig control that could be spent on anything, whenever governance or the team decided to. A scheduled unlock is a known quantity. An unscheduled reserve is an open-ended option written against every holder, and markets discount open-ended options harshly because they can't model them.

That's what the burn removed. Not supply, but discretion.

Sanctum Removed a Real Risk, Just Not the One in the Headline.

Concede the protocol's point fully. An overhang doesn't have to be sold to depress a price. Its mere existence caps what new buyers will pay, and a team that burns tokens it could have spent is giving up something real. Sanctum also didn't decide this alone. The burn passed through MetaDAO's futarchy markets, where traders put capital behind "pass" and "fail" outcomes and the proposal executed because the pass market priced higher. Holders were asked, with money, whether the token was worth more without the reserve. They said yes.

Still, look at what stayed. The governance record shows a team reserve of about 115.6 million tokens kept for future compensation, plus about 105.6 million in vesting pools running through July 2027. When community members pushed for part of the team's strategic reserve to be burned too, as a signal of shared commitment, Sanctum declined, saying the reserve "is needed to attract and retain talent." Another holder put the critique more sharply during the vote: "Holders revenue is still $0."

Both responses are defensible. A protocol that reports $2.05 billion in total value locked and $4.53 million in trailing net revenue does need to pay people. But it means the discretionary supply problem got smaller, not solved. The tokens that could still show up without warning are now the team's, not the community's.

Streamflow Showed What a Burn Looks Like When It Costs Something.

For contrast, consider the Streamflow Foundation, which runs token-lock and vesting infrastructure on Solana. In late September it burned 699.99 million STREAM, 70% of total supply, at the mint level. The burn took 100% of the foundation's allocation, locked and unlocked portions alike, plus a significant portion of the founder and future team allocations.

That last part is the difference. Streamflow didn't only destroy tokens nobody had a claim on. It destroyed tokens its own people would otherwise have received. The remaining supply is now mostly accounted for in disclosed buckets, with 11.47% in investor and contributor vesting contracts and 4.03% left for current and future team members. CEO Mališa Stanojević framed it as removing the treasury as a variable the market has to price: "Burning it outright is the only version of this commitment that doesn't depend on anyone's continued good intentions."

That sentence is the whole argument. A reserve promise depends on good intentions. A vesting contract with a public schedule, or a time lock anyone can verify on-chain, depends on code. A burn depends on nothing at all. The further a project moves its supply from the first category into the other two, the less the market has to guess.

Regulators Are About to Make Every Reserve Visible.

This won't stay a matter of taste for long. The SEC's proposed Regulation Crypto Assets, published in August with comments due October 20, would require issuers using its new exemptions to disclose token supply, allocation, lockups, release schedules, and "methods of creation or destruction," along with insider resale restrictions. Final rules aren't expected before next year and could change. But the direction is clear. The question every token buyer should already be asking, which tokens exist and who decides when they move, is on its way to becoming a disclosure line item.

When it does, headline burn percentages will matter less than a simple ratio: how much of a token's supply sits on a schedule anyone can read, and how much still waits on someone's decision. Sanctum just moved 259 million tokens from the second column to nowhere. The projects that get rewarded next will be the ones that empty that column before they're made to.