Polkadot News: DOT DAO Approves 100% Burn of JAMKB Revenue
Crypto News Today: Polkadot DAO Approves Total JAMKB Burn in Referendum 1926
In the latest Crypto News Today, this piece of Polkadot news covers a fresh governance outcome that could reshape how supply behaves once the JAM upgrade goes live.
The DAO passed Referendum 1926 on the Wish for Change track, voting to 100 percent of the revenue collected from future JAMKB sales instead of sending it to the network treasury.
Polkadot confirmed the result through its official X account on August 24, 2026. 
The referendum further states that the resource should not be handed out through grants or below market loans, a detail every reader following DOT should note as part of this update.
What This Wish for Change Vote Actually Decides
Referendum 1926 runs on the Wish for Change track, a lane the DOT DAO vote uses to signal intent rather than push code directly. This round of Polkadot governance confirms three points from the passed text:
Coins collected from any sale, lease, or rental of JAMKB get earmarked for a JAMKB, not treasury growth.
The resource will not be distributed through grants.
The resource will not be offered through below market loans.
Web3 Foundation contributor Bill Laboon addressed the outcome too, calling the resource an allocation tool rather than a stand in for the native asset itself, a framing shared in a community digest post the community treated as an official update.
Treasury Route Versus Burn Route
Path | What Happens to the Funds | Effect on Supply |
Send to treasury, rejected | Funds sit with the DAO for future spending | Supply stays flat |
Burn all revenue, approved | Coins leave circulation for good | Supply shrinks over time |
The table above sums up the tradeoff voters weighed, and it feeds directly into wider Polkadot tokenomics talk following the March 2026 supply cap, another storyline regular readers of this news desk have followed closely.
Why This DOT Burn Mechanism Stands Out
Unlike routine fee burns, this proposed DOT token is tied to a brand new resource that represents limited state space on the coming JAM upgrade.
The scale of the eventual burn depends entirely on how much builder demand shows up once the network launches.
The original post on the outcome was later echoed in a second update from the Web3 Foundation team, screenshotted below for reference, and it quickly became one of the more shared threads in DOT circles this week.
What Referendum 1926 Does Not Do
This vote is a signal, not an execution. The track does not deploy any runtime code by itself. Two points the community keeps flagging on the forum:
The token itself remains a proposal, it has not launched yet.
No burn code exists yet, so a separate technical referendum must still define exactly how the burn works, an idea already floated in a forum proposal for a burn account.
Market Reaction and What Comes Next
DOT price around the vote has been mixed, with traders weighing the long term supply story against short term questions over the mainnet timeline.
For now, this remains one of the more closely watched threads in crypto news this week among followers, since it sets the tone for how future JAM era revenue gets treated.
This Polkadot news outlet will keep tracking the process as the community moves from a signaling vote to an actual coded mechanism.
Readers can expect more Polkadot news coverage as the technical referendum for the real burn mechanism takes shape in the coming weeks, alongside any fresh word from the Web3 Foundation or the core development teams building the JAM stack.
Disclaimer: This article reports on an ongoing DAO governance vote. Please note that signaling votes do not guarantee the immediate deployment of technical code. The content provided is for purposes only and should not be construed as investment advice. Readers should do their own research before interacting with any digital assets.
