Cronos Burned 228 Million CRO With a Vote. Today Its Reserve Releases Five Times That.

On October 3, Cronos holders sent 228 million CRO to a burn address. The vote passed alongside a second proposal that drew 99.78% approval, pledging every dollar of revenue from the network's new trading app and launchpad to open-market buybacks. The tokens were worth about $15 million, and the community program's lifetime burn total rose to 428 million CRO.

Today, October 17, the Cronos Strategic Reserve is scheduled to vest about 1.17 billion CRO, worth roughly $70 million. It did the same thing last month. It will do it again next month, and the month after that, for years.

Five times the burn. In a single tranche.

The burn is the headline, but the reserve is the actual supply policy.

The arithmetic is not hidden. CryptoTicker ran it plainly last week: one monthly tranche is about 2.7 times every community burn Cronos has ever done, and roughly 2.4% of circulating supply, against just under 0.5% for the burn. What deserves more attention is where that reserve came from, who now draws on it, and what the October vote quietly changed about its job.

The reserve is made of tokens Cronos already destroyed once.

In 2021, Cronos burned 70 billion CRO, cutting supply from 100 billion to 30 billion in what The Block called one of the largest burns in crypto history. In March 2025, Cronos Labs proposed bringing all 70 billion back into a "strategic reserve wallet." At the time, the circulating supply was 27.3 billion CRO.

The vote was ugly. According to Mintscan records cited by The Crypto Times, 95.7% of participating voting power opposed it on the first day. It passed on March 16, 2025, with 62.1% in favor, after a late wave of votes pushed participation to about 70%. The re-minted tokens went into escrow, set to release in monthly tranches of roughly 1.17 billion CRO. Reporting still disagrees on whether that schedule should be read as five years or ten, but the tranche size is consistent across trackers, and 60 of them adds up to 70 billion.

CoinGecko now puts circulating supply at about 49.5 billion CRO. So in roughly 19 months, the float has grown by more than 22 billion tokens. Against that, 428 million burned is not a counterweight. It is a rounding adjustment.

October's vote made the reserve the payroll for stakers.

Read the second proposal closely. Proposal 37 did not just route revenue to buybacks. Because every dollar of product revenue now goes to burns, staking rewards needed a new funding source, and the proposal named one: the 70 billion CRO Strategic Reserve. Reward rates, tiers and lock periods stay the same for delegators. The money behind them now comes from the re-minted pile.

The proposal set no cap on how much the reserve can pay out for staking, no time frame, and no plan for what happens if revenue disappoints. It also published no revenue figures for either product. The buy-and-burn contract itself was listed as "in development" when holders voted.

Put the two halves together and the structure looks like this. A small, unquantified revenue stream buys tokens and destroys them, with every transaction hash published for applause. A large, scheduled stream of tokens Cronos once destroyed flows out to the people who vote on what happens next. Stakers get their yield, the burn gets its headline, and the net supply keeps rising.

Concede the industry's point: a vesting release is not a market sale.

Cronos's defenders have a fair argument, and it deserves a straight hearing. A tranche vesting into a reserve wallet is not the same as 1.17 billion tokens hitting an order book. CryptoTicker made exactly this point: a reserve release is not a sale. Paying stakers from an existing pool, rather than minting fresh emissions, is arguably more honest than inflation dressed up as yield. And a revenue-funded buyback with published hashes is more accountable than most token "burns," which tend to destroy tokens nobody was ever going to sell.

All of that is true. None of it changes the thesis.

Tokens paid to stakers are circulating tokens. Some get restaked, some get sold, and the reserve has no published ceiling on how fast it can be drawn down for that purpose. The buyback is only as large as revenue that nobody has disclosed. Ult, the rebranded trading app, launched September 17 in more than 100 countries, and Cronos Launch, the launchpad, opened two days earlier. A month in, the only hard numbers in this story still belong to the unlock schedule.

A chain that can rewind two hours can rewrite a supply schedule too.

There is a second reason to treat Cronos's tokenomics as a policy choice rather than a law of nature. On August 30, an attacker inflated the price of Tectonic's thinly traded TONIC token and borrowed $120.4 million across nine markets against it. Validators halted the network and rolled it back 10,961 blocks, discarding 1 hour and 54 minutes of history, legitimate transactions included. The rollback reversed about $111.2 million. Roughly $9.19 million had already left the chain and was not recovered.

Cronos's developers called it a hard decision, arguing the alternative would have left the borrowed assets with the attacker. That is a defensible call. But the episode is a reminder of who actually sets the rules here. The same validator set and governance machinery that un-burned 70 billion tokens, and that can erase two hours of blocks, now decides how fast the reserve pays out and what counts as a burn worth celebrating. Holders are not reading a fixed schedule. They are reading the current intentions of a small group that has shown it will change course when it decides it should.

That is not a scandal. It is a design. It just isn't the design the burn headlines describe.

The honest version of this tokenomics would lead with the reserve.

None of this requires bad faith from Cronos Labs. It requires a disclosure order that matches the economics. If a project wants holders to weigh supply honestly, the monthly vesting tranche, the reserve's remaining balance and the staking drawdown belong at the top of the dashboard, with the burn below them. Teams launching new tokens can do this from day one by putting allocations into publicly verifiable vesting and lock contracts that anyone can check without waiting for a tracker to flag the date. Projects choosing where to launch should expect that scrutiny, and buyers should demand it.

For Cronos, the next test is simple and close. The first monthly buyback under Proposal 37 should arrive with a transaction hash and a revenue figure attached. Put that number next to 1.17 billion. If the gap is as wide as it looks, holders will know which half of the October vote really sets the supply, and it won't be the half that burns.