Cronos V5 restored CRO supply to 100 billion tokens

Cronos POS completed its V5 network upgrade on March 18, 2025, implementing a governance decision to allocate 70 billion CRO to a new strategic-reserve escrow account. The change restored CRO's nominal total supply from about 30 billion to its original 100 billion level, reversing in economic effect the 70 billion-token burn announced in 2021.

The scale made this more than a routine software release. The 70 billion allocation was about 233% of the pre-upgrade 30 billion supply base. It also represented 70% of the resulting 100 billion total. Those are arithmetic comparisons of token quantities, not estimates of immediate circulating supply or market value: the reserve was created as a vesting account, so the entire allocation was not freely transferable on March 18.

What the vote authorized

Cronos governance proposal 29 was submitted on March 3, 2025 and its voting period ended on March 17, according to the chain explorer. The official proposal described the V5 upgrade as a package: create the strategic reserve, lower the mint module's maximum inflation parameter from 3.7% to 1%, and lower its minimum from 1.2% to 0.85%.

The proposal said the reserve could support U.S.-focused ecosystem initiatives, traditional-finance crossover projects, a possible CRO exchange-traded fund, artificial-intelligence development, grants and developer tools. Those were the proposer's stated intentions on March 3, not verified commitments by a fund sponsor, exchange or U.S. regulator. Nothing in the vote constituted an ETF filing or approval.

The contemporaneous voting record, as reported on March 18, showed 62.1% yes, 17.6% no, 20.1% abstain and 0.11% no-with-veto; the displayed shares are rounded. Turnout exceeded 70%. Reporting also showed that several large validators supplied decisive voting power after the proposal had struggled to reach quorum. The on-chain result verifies passage. It does not by itself identify the beneficial owners behind validator votes, so claims about who controlled the outcome remained allegations rather than established facts on March 18.

Supply was not the same as liquidity

The proposal specified a Cosmos SDK periodic vesting account. It scheduled approximately 1.167 billion CRO to vest every roughly 30.4 days, or 2,628,000 seconds, across the five-year release program. The proposal also said reserve tokens were not intended to be delegated while held in escrow.

That structure matters when interpreting dilution. V5 changed total supply immediately at protocol level, while transferability was scheduled over time. A 233% increase in the nominal supply base therefore should not be described as a 233% one-day increase in tradable float. Nor can the token quantities alone establish a dollar value: any valuation would require a named CRO price venue, timestamp, circulating-supply definition and liquidity assumptions. This reconstruction makes no price claim because the surviving primary records do not provide a sufficiently specified event-time market window.

Why March 18 mattered

Token burns are commonly presented as permanent reductions in supply. Cronos demonstrated that a blockchain's later governance process could change protocol accounting and recreate an equivalent quantity, provided validators adopted the upgrade. That made governance concentration, upgrade authority and the legal or social meaning of “burned” tokens central risk questions for CRO holders and protocol observers.

The strongest conclusion available on March 18 was narrow but consequential: V5 had changed CRO's supply framework and assigned most of the resulting total to a purpose-limited reserve with scheduled vesting. Whether the reserve would produce the adoption, institutional access or ecosystem growth described by its sponsor remained unverified and depended on later execution.