Polkadot (DOT) Treasury Spending decides which developers, event organizers, and community projects receive money from a pool that the network itself controls.
No individual holds the keys to that pool, and every payout needs a passed vote through OpenGov, the on-chain governance system where DOT holders decide network matters.
Interest in Polkadot Treasury Spending has grown because the network reworked its economics earlier this year. Fewer new tokens now flow in, and the old periodic burn is gone.
The treasury is a pot of DOT held in a system account, which means no external wallet can move it. Only the network's own logic releases funds, and it does so only after a referendum succeeds.
Polkadot Treasury Spending therefore reflects what token holders collectively decide is worth paying for. The official treasury documentation describes the pool as a shared resource for grants, development work, events, and security fixes.
Matching a grant to a live product is easier with the app listings on Polkadot's official website, which catalogs apps across the ecosystem.
The documentation lists four inflow routes. Three work automatically, and one is voluntary.
Inflow source | How it works |
Transaction fees | 80% of fees from submitted extrinsics go to the treasury, and 20% to block producers. |
DOT inflation | 15% of annual inflation is directed to the treasury. |
Slashing | A share of slashed tokens is diverted, though slashes are rare and unpredictable. |
Direct transfers | Any account can send funds, usually grantees returning unused amounts. |
Inflation is also the source of rewards for Polkadot staking, so the split between stakers and the treasury is a design choice rather than a fixed fact of nature.
Outflow runs the other way. Approved proposals and bounties take the largest share and are paid when a spend period ends, while small tips can be paid inside a period.
One caution applies here: under the 2026 update, fees, coretime revenue, and slashes are reported to flow into a new Dynamic Allocation Pool first, so the shares above may have shifted. Live on-chain values should be checked before anyone relies on them.
Approval follows a fixed path, and the path changes slightly with the size of the request.
OpenGov manages treasury requests through six tracks: Treasurer, Big Spender, Medium Spender, Small Spender, Big Tipper, and Small Tipper. Each track has its own origin and parameters, so a small request faces lighter requirements than a large one.
A proposer needs a verified on-chain identity, then submits a preimage, which is a stored record of the exact spend. A decision deposit follows, and only then does the referendum move into its deciding phase.
Payouts no longer have to arrive as one lump sum. A staged proposal can split funds into tranches that become redeemable at set block heights, and governance can void the remaining tranches before the final payment.
According to the step-by-step treasury guide, each spend must be claimed manually within 30 days once it becomes valid.
Bounties cover recurring needs. A parent bounty reserves funds once, a curator (usually a multisig account) manages them, and child bounties pay out without a new referendum each time.
The documentation also notes that the treasury can spend assets beyond DOT, such as USDT on Asset Hub, after governance approves the asset and sets a conversion rate.
On March 12, 2026, a runtime upgrade passed Referendum 1710. Implemented a hard supply cap of 2.1 billion DOT, removed the periodic treasury burn, and created the Dynamic Allocation Pool for fees, coretime revenue, and slashes. Gross issuance then fell by 53.6% from March 14, 2026, stayed flat for two years, and afterward stepped down by 13.14% of the remaining supply every two years.
Before the change, one percent of treasury holdings was burned every 24 days, according to figures posted in community proposals.
The same proposals estimated that treasury income from issuance would drop from roughly 18 million DOT a year to about 8.3 million. That number is a community estimate, not an official budget.
The practical result is straightforward. Unspent funds now stay available, but less money arrives each year. That shifts attention from how fast the treasury spends to how well each approved request performs.
Several patterns can show where ecosystem money is heading. None of them comes from a single official dashboard, so each needs checking against live governance data.
Milestone payouts: the share of proposals that use staged tranches instead of lump sums.
Stablecoin requests: USDT spends protect grantees from DOT price swings.
Bounty activity: child bounty volume shows whether curators spend steadily or hold funds.
Track mix: whether small- and medium-spender referenda dominate while big-spender requests become rarer.
Balance versus income: whether the treasury balance grows now that the burn has stopped.
The Polkadot Developer Interface displays the current spend period under its treasury tab, and governance apps list recent referenda by track. Together they give a rough picture of how ecosystem grants are moving month to month.
Smaller inflows are the central concern. With issuance reduced under a token supply cap, the treasury has less to distribute, which could raise the bar for approvals or slow funding for newer teams.
A passed referendum also does not guarantee a delivered product, so results matter more than votes.
Voter turnout is a second unknown. Proposals are decided by whoever votes, and low participation can concentrate influence among a few large holders. That is an analyst interpretation, not a confirmed pattern.
Token price adds another layer. The treasury holds mostly DOT, so the DOT price outlook shapes how much a fixed grant is worth to the team receiving it. Growth in stablecoin payouts may partly reflect that concern.
Data freshness is the last issue. Documentation can lag network upgrades, as the older burn description shows. Any figure in this article should be verified on-chain before it enters research or reporting.
Polkadot Treasury Spending follows a clear chain: income arrives, OpenGov votes track the bar, and payouts come as lump sums, tranches, or bounties.
The 2026 update changed the income side by ending the burn and cutting issuance, which leaves budgets smaller but no longer reduced by automatic destruction.
What remains uncertain is how voters will prioritize spending less and whether funded work reaches real users.
Live treasury balances, recent referendum results by track, and the status of active bounties are the next items to check.
Disclaimer:
This article is for information only and is not financial, legal, or investment advice. Crypto assets are volatile and high-risk, and governance outcomes can change. Independent research is needed before any decision involving DOT.