Jupiter burned 3 billion JUP after DAO supply vote

Jupiter executed a burn of 3 billion JUP tokens on January 26, 2025, completing the central action in a supply-reduction plan approved by its decentralized autonomous organization in August 2024. The Solana transaction and Jupiter’s later allocation audit establish the burn; the project’s Catstanbul agenda tied it to the conference’s second-day closing ceremony in Istanbul.

The quantity equaled 30% of the 10 billion-token supply framework described in the governance proposal. Under that proposal, 1.5 billion JUP came from team-managed allocations and 1.5 billion from community-designated allocations, reducing the planned total to 7 billion. That arithmetic describes token supply, not a 30% reduction in the tradable float: the burned units came from controlled allocation buckets rather than tokens already circulating in public markets.

A governance decision became an on-chain action

Jupiter’s August 1, 2024 proposal framed the cut as a response to uncertainty over future emissions and fully diluted valuation. It specified reductions from liquidity needs, the team allocation, strategic reserves, Mercurial stakeholder allocations, future “Jupuary” distributions and community reserves. A contemporaneous Jupiter community tally reported that the proposal passed with 260,131,475 JUP voting for it, 9,382,737 against and 4,519,713 abstaining; the displayed shares were 95%, 3% and 2% after rounding.

January 26 therefore mattered less as the date of a new vote than as the date Jupiter carried out the previously authorized accounting change. A token burn destroys units through the token program so they can no longer be transferred. It does not remove the protocol’s ability to change other emission schedules through later governance, and it does not by itself create usage, cash flow or demand.

Jupiter’s February 2025 community audit, published after the event, traced the 3 billion JUP into a dedicated burn multisig and linked the final burn transaction. It broke the amount into 582.7 million and 917.3 million JUP from team-controlled wallets, plus 1.1 billion and 400 million JUP from community-controlled wallets. Those four components sum to 3 billion. The audit is an involved party’s record, but the linked Solana transaction independently anchors the destruction on-chain.

Buybacks were announced, not yet demonstrated

At Catstanbul, Jupiter’s pseudonymous co-founder Meow also announced that 50% of protocol-fee revenue would be used to buy JUP from the market and hold the acquired tokens in a long-term “litterbox.” The other half was described as funding growth, strategy and operating stability.

That was a contemporaneous policy announcement, not evidence on January 26 that purchases had started, how frequently they would occur or which fee streams would qualify. The distinction is important: the 3 billion-token burn was verifiable execution, while the buyback mechanism still depended on implementation and transparent accounting.

The Block reported at 11:55 a.m. Eastern that JUP rose about 40% from an intraday low near $0.90 to about $1.27 before easing. Its report did not identify a trading venue, quote timestamp or daily-candle boundary, so those figures are best treated as a rounded event-day indication, not a universal market return. Crypto trades continuously and prices differ by venue.

What the burn did—and did not—prove

The burn reduced future dilution embedded in Jupiter’s stated allocation plan and demonstrated that a DAO-approved tokenomics change could be executed on-chain. It did not prove that every voter had equal influence, that JUP’s market value would rise, or that the announced buybacks would be sustainable.

The defensible January 26 conclusion is narrower: Jupiter permanently removed 3 billion JUP from the token supply and paired that completed action with a new fee-funded buyback commitment whose operation remained unverified on the event date.