Sanctum Opens 72-Hour MetaDAO Vote to Burn 259 Million CLOUD Tokens
Sanctum opened a MetaDAO futarchy vote to burn 259 million CLOUD tokens,
Sanctum CLOUD$0.061+5.8% opened a 72-hour MetaDAO futarchy vote on September 16 on whether to burn 259 million CLOUD tokens remaining in its Community Reserve, which would cut total supply by roughly 25%.
The vote, labeled CLOUD-008, went live at 08:12 UTC and closes around September 19. Participants trade the decision market on MetaDAO META$5,290.23-0.1% at metadao.fi/decisions/sanctum-010. The outcome follows whichever conditional market, burn passing or burn failing, holds the higher price at expiry.
What CLOUD-008 Proposes: 259 Million Tokens From an Idle Reserve
The target is the Community Reserve created at the CLOUD launch in June 2024 to fund incentives and community distribution. Of the original approximately 307 million tokens in that reserve, roughly 48 million were distributed: 45 million through the Active Staking Rewards program and about 3 million in vault incentives. Sanctum ended that staking program in August 2026. The remaining 259 million tokens have no programmatic purpose, according to the official proposal.
If approved, those tokens would be permanently destroyed, reducing total supply from approximately 1 billion to roughly 741 million. Solana Compass tracks 79,223 wallets holding CLOUD as of September 16.
The team's Strategic Reserve of roughly 110 million tokens, earmarked for compensation, talent, and future grants, is outside the proposal and would not be burned, per the same official proposal. Some community members raised this point in the September 2 forum period, arguing the burn should include a partial team token reduction to signal shared commitment. Sanctum responded that the Strategic Reserve is needed to attract and retain talent.
CLOUD-to-SANC Ticker Rename: A Team Announcement Outside the Vote
Alongside the MetaDAO submission, Sanctum announced that the token ticker will change from CLOUD to SANC. That change is a metadata update covering name, symbol, and logo, with no effect on the mint address, tokenomics, or token economics. It does not require governance approval and is not part of CLOUD-008.
The stated reason is discoverability. According to the proposal, searching "CLOUD" on CoinGecko or CoinMarketCap returns Google Cloud and Alibaba Cloud results prominently, making the Sanctum token difficult to locate by name.
Sanctum's Case: The Reserve Has Done Its Job
The Community Reserve was created to bootstrap the protocol through incentives and staking rewards. With that program concluded in August 2026, the team's position is that the remaining balance has no remaining function.
The team attributed the gap between business performance and token performance to three factors: supply dilution from staking rewards already distributed, the remaining token overhang from the Community Reserve, and a ticker that doesn't connect to the protocol name. The CLOUD-008 proposal addresses the first two; the rename addresses the third.
Sanctum reached Solana's top DeFi TVL position in August 2026 with 18 million SOL staked and has been profitable since 2025.
The full proposal and FAQ were published on September 2 when the team submitted CLOUD-008 for community review ahead of the on-chain vote.
How MetaDAO Futarchy Determines the Outcome
CLOUD-008 runs through MetaDAO's futarchy mechanism rather than a standard token-weighted poll. In futarchy, two conditional markets trade in parallel: one representing the token's value if the proposal passes, one if it fails. The proposal executes if the pass market ends at a higher price than the fail market. Participants stake capital to express their view, rather than casting costless votes.
Sanctum has used the MetaDAO mechanism for previous CLOUD governance decisions, including the August 2026 vote that approved the final 15 million CLOUD distribution to wrap up the Active Staking Rewards program, per the official proposal.
Community Counterarguments: Burn Without Revenue Accrual
The community response since September 2 has centered on a recurring argument: burning supply addresses the overhang while leaving token value accrual unresolved. Multiple replies questioned whether reducing supply moves the needle when the protocol earns revenue that still does not reach token holders.
"Burn the 259M. Then put real revenue into buybacks," one community member wrote. "Holders revenue is still $0. Fix that and the market will notice."
Sanctum has not included revenue sharing or automatic buybacks in CLOUD-008. The team has expressed support for buybacks in principle but prefers timing them to market conditions rather than automating them. CLOUD-008 addresses the supply overhang; the revenue accrual question remains open and separate.
The MetaDAO vote closes around September 19, 2026 at approximately 08:12 UTC.
Comments
Please login to leave a comment.
Contents
Related Content
How MetaDAO Became Solana's Breakout Token Launchpad | Kollan House
Exploring Futarchy: Governance by Markets with MetaDAO's Proph3t
Sanctum Founder: Solana's Liquid Staking Future | FP Lee
Sanctum Burns Its CLOUD Community Reserve, Cutting Token Supply to 740.7 Million as SANC Ticker Appears
MetaDAO (Pt 2): The Start Of A World-Changing Governance Experiment ๊พ Nallok & Prophet, MetaDAO
The Most Exciting Experiment In Crypto: Futarchy | Robin Hanson & Proph3t
Sanctum Governance Vote Passes: 259M CLOUD Tokens to Be Burned, Ticker Renames to SANC
The Future of Liquid Staking on Solana | FP Lee
Solana's Sanctum App 2.0 Launches With Squads Multisig Protection on iOS, Android and Seeker
Product Keynote: MetaDAO
What Futarchy Looks Like in Practice w/ Kollan House (MetaDAO)
Sanctum Proposes Burning 259M CLOUD Tokens and Renaming Ticker to SANC
The One With Kollan from MetaDAO | ep. 4
Building A World Free Of Currencies - Prophet (MetaDAO)
Ship or Die at Accelerate 2025: Lightning Talk: MetaDAO
Latest news
VanEck Solana ETF (VSOL) Declares First Cash Distribution of $964,960 From Staking Income
Jupiter's Swap API Adds Opt-In Solana Transaction v1 Support for Integrators
Orca Tokenholders Vote on Cutting xORCA Rewards to 10%, Moving 14.2M ORCA to the Team and Dissolving the Council
Triton One Publishes Alpenglow Integrator Guide: What Solana RPC, gRPC and Indexing Users Must Change
Solana's 200ms Slot Time Is Pending on Mainnet, Scheduled to Go Live at Epoch 1053 on October 9
Circle's USDC Bridge Adds Solana, Linking It to 18 Other Chains
Solana Foundation Announces @solana/web3.js v3, a Kit-Based Rebuild of the Classic JavaScript API, With a New Wallet Adapter
Kamino Opens Apyx Market, Letting apyUSD Holders Borrow USDC on Solana
Venice Token (VVV) Goes Live on Solana via Sunrise, Connected by Wormhole NTT
MagicBlock Releases Validator v1.0 for Ephemeral Rollups on Solana, With New Session and Commit Fees
Solana Token Markets