DOT is a security budget token first, governance token second, blockspace token third

Polkadot’s DOT design is blunt about what it rewards. If you help secure the relay chain, you get paid. If you help steer the protocol, you get control. If you want guaranteed execution resources, you pay for coretime.

Polkadot’s own documentation frames DOT around three main functions: governance, staking, and access secure computation via purchasing coretime.

From an incentive-alignment perspective, the design choice that keeps showing up is this: Polkadot pays for security largely via issuance, and it routes a meaningful, protocol-defined share of economic flows into governance-controlled pots. That is coherent. It is also where most failure modes live, because “governance-controlled pots” are exactly where incentives get vague and extractive behavior can hide.

Two structural shifts matter for how DOT behaves today. First, parachain slot auctions were replaced by the coretime marketplace with a runtime upgrade on September 19, 2024. Second, Polkadot moved to a fixed annual emission number and later approved a hard cap and a stepped issuance reduction schedule.

If you are modeling DOT, you should treat it like a system where monetary policy is a product surface. It is adjustable by OpenGov. Parameter stability is not guaranteed. The upside is adaptability. The downside is governance risk, which becomes the dominant risk once the chain is credibly decentralized. For a useful contrast in how an L1 treats inflation and governance, see our NEAR tokenomics review.

Supply, issuance, and the cap: the rules changed, and the direction changed

The cleanest way to think about DOT supply is in layers: (1) genesis distribution history, (2) redenomination mechanics, (3) ongoing issuance and its recipients, (4) sinks like burns, and (5) the newly approved cap and stepped reductions. If you want a general evaluation framework, start with our design principles.

Polkadot redenominated DOT on August 21, 2020, where 1 “old” DOT became 100 “new” DOT. This did not change ownership fractions. It changed unit scale and UX.

On current market data, CoinGecko lists circulating supply 1,671,956,416 DOT, total supply 1,671,956,416 DOT, and max supply 2,100,000,000 DOT (as displayed on March 6, 2026).

Polkadot’s wiki describes a post-2024 model with a fixed annual expansion of 120,000,000 DOT, split 85% to stakers and 15% to the treasury. The Polkadot Support documentation also describes how this constant-emission implementation was finalized via a runtime upgrade (v1.3.4) after the 2024 referenda series.

The more recent shift is governance-approved supply constraint. Polkadot Support states that Polkadot now has a fixed maximum supply of 2.1 billion DOT and points to Referendum 1710 (“Hard Pressure”) as the driver of the cap and stepped issuance schedule. A Polkadot Forum recap ties this to an on-chain Wish for Change approved on September 14, 2025, with the first issuance reduction on March 14, 2026, dropping annual issuance from 120 million DOT to 55 million DOT.

Mechanically, the incentive intent is clear. Reduce dilution. Make security spend more “budget-like.” Force the ecosystem to justify itself with paid demand and governance discipline, not reflexive inflation. For a clean hard-cap reference point, compare against our Litecoin tokenomics review.

Distribution still matters because it determines who can realistically steer OpenGov and who is structurally overpaid by any issuance-based model. Publicly available documents that summarize the reported genesis distribution break it down as follows (presented here as “reported distribution” rather than as a protocol-enforced truth, since allocations are ultimately reflected by balances and custody).

I do not like relying on non-protocol sources for allocation tables. But the incentive question remains valid even if you ignore category labels and just treat it as “large, early, concentrated balances exist.” In Polkadot, large balances do not just imply price impact. They imply governance and treasury control surface area.

Who earns DOT, and for what behavior

DOT issuance is not “value accrual.” It is a payment system. You should ask who is being paid, for what actions, and whether the paid party can externalize costs onto everyone else. For a different “payment for service” style of token design, see our Chainlink tokenomics review.

Under the fixed annual expansion described on the Polkadot wiki, 85% of the 120,000,000 DOT/year goes to stakers. In Polkadot terms, that means validators and nominators who bond DOT to secure the relay chain through staking.

The remainder is not “retained earnings.” It is a governance-controlled budget line. The same wiki page states 15% goes to the treasury. And the treasury documentation explicitly lists its inflows, including inflation and fees.

Transaction fees are also an ongoing payment stream. Polkadot’s treasury documentation states that 80% of transaction fees are diverted to the treasury and 20% are given to block producers. This is a very explicit incentive decision: routine network usage largely funds a governance pot, while block authors get a smaller direct fee cut.

Staking adds classic proof-of-stake discipline, but with Polkadot-specific operational quirks that matter for incentives. Staking rewards are not automatic. Someone must trigger payouts, and rewards are available for a limited time. The wiki notes rewards must be claimed from Polkadot Hub (Asset Hub) and that rewards are kept available for 84 eras. That creates a “maintenance tax” on passive nominators and pushes delegation toward operators and tooling providers who reliably handle payouts.

On slashing, Polkadot’s staking docs state that in NPoS, both validators and nominators can be slashed in an attack scenario, and slashed funds are deposited to the treasury. The March 2026 recap indicates that with the upcoming DAP work, validator slashes will be directed to the DAP, and treasury burns will stop with tokens instead sent to the DAP. This is not cosmetic. It changes who benefits from misbehavior penalties and what “fiscal policy” means on-chain.

Finally, governance can rewrite the rules. That means the “who earns DOT” answer is not static. It is a moving equilibrium shaped by OpenGov incentives, voter turnout, delegation habits, and the ability of sophisticated actors to propose and pass parameter changes.

Fees, coretime, and burns: the fiscal plumbing that DOT holders actually feel

Polkadot’s economics are increasingly about flows, not just issuance. You can read it like a public-sector budget with two big revenue lines (issuance and fees) and one big emerging demand line (coretime).

Fees. Polkadot uses weight-based fees, charged before execution, and can apply a fee multiplier when the network is busy. The tokenomics-relevant part is not the exact base fee. It is the fee split. Again, 80% to treasury, 20% to block producers. This makes the treasury a first-class recipient of user-paid value.

Treasury “burns.” Historically, Polkadot had a treasury burn mechanism. The current chain state values page shows the Treasury Burn Factor is 0.0% at the end of each spending period. The March 2026 recap provides a reasoned direction: treasury burns will stop and instead the DOT tokens will be sent to the DAP. Incentive-wise, this is a pivot away from “auto-deflationary discipline” and toward “explicit budget reallocation.” It increases governance power over supply sinks. That can be good. It can also be a magnet for rent-seeking.

Coretime, and why it matters more than parachain auctions ever did. With Agile Coretime, Polkadot sells execution resources as a product. Bulk coretime is represented by NFTs, and the wiki states that the duration of bulk coretime is currently 28 days. The same wiki documents that auctions ran until the Agile Coretime runtime upgrade on September 19, 2024.

The most important economic decision around coretime is what happens to the revenue. Polkadot Fellowship RFC-0010 (“Burn Coretime Revenue”), dated July 19, 2023, argues that revenue from coretime sales should be burned, explicitly framing this as “collective value accrual” by reducing issuance and benefiting all token holders equally. A Parity data “End of Year 2024” report states that early coretime sales revenue on Polkadot (including the first purchase on October 6, 2024 at 69 DOT) was burned, and notes total revenue of approximately 844 DOT burned at the time of reporting.

That burn choice is one of Polkadot’s best-aligned tokenomic mechanisms. It ties adoption to a supply sink without forcing “ecosystem spending” narratives to do the work. It is also not free. Burning revenue means validators do not directly earn from coretime demand. The security budget remains issuance-heavy unless governance later redirects other flows.

The hidden tension: users pay fees that mostly go to a governance pot, while builders pay coretime that is burned. This splits “who benefits” across two worlds. Token holders benefit from coretime burns in a diffuse way. Treasury beneficiaries benefit from fee flows in a very direct way. If you are trying to predict political economy, that asymmetry matters.

Governance control surfaces: OpenGov is DOT’s monetary policy committee

OpenGov is not just “token voting.” It is the mechanism that can rewrite inflation, fee routing, treasury policy, and operational parameters. DOT’s long-run credibility depends on whether OpenGov outcomes are legible, hard to capture, and resistant to short-term extraction.

Polkadot’s OpenGov system uses origins and tracks, with different parameters and different throughput per track. The Polkadot wiki’s OpenGov origins page shows, for example, that the Root track has Max Deciding 1 and a decision deposit of 100,000 DOT. That design choice is intentional friction for high-privilege changes.

Voting power can be increased via voluntary locking. The Polkadot wiki describes conviction voting where votes equal tokens × conviction multiplier, and provides the lock schedule up to 32 lock periods and a 6× vote multiplier. The chain state values page states that one conviction voting lock period on Polkadot equals 7.0 days. So the maximum conviction lock described on that schedule corresponds to 224 days when using 32 periods.

OpenGov’s tally logic is also more complex than simple majority. Approval is conviction-weighted. Support is turnout-like and counts aye and abstain but not nay. That has real incentive effects. For sophisticated actors, the game becomes “get over both curves for long enough,” not “win a snapshot vote.”

Delegation makes this more scalable and more capture-prone at the same time. The wiki describes multirole delegation where accounts can delegate by track. This improves governance throughput for passive holders. It also centralizes influence into delegate brands, which can become de facto political parties without the transparency obligations of institutions.

The March 2026 recap underscores how deep governance now reaches into “operational economics.” It discusses validator-side changes such as a proposed minimum self-stake of 10,000 DOT and a minimum commission of 10%, expected to be enacted via subsequent referenda after the runtime upgrade window around March 23-27, 2026. Whether you like those choices or not, they demonstrate the reality: DOT’s incentive model is actively governed, not passively encoded.

Risk register: incentive alignment failure modes

Polkadot’s token design is ambitious and explicit. It is also governance-heavy. That makes it unusually sensitive to incentive drift. Here are the top risks that I think matter most to DOT holders and builders, ranked by how likely they are to create persistent economic damage rather than short-term volatility. We publish related governance and incentive analyses in our research reports.

Top 3 risks

  1. Governance capture of fiscal flows.
    Trigger: delegation concentration, low turnout on high-impact referenda, or coordinated voting blocs accumulating conviction locks.
    Mechanism: OpenGov can steer treasury policy, issuance policy, and new pots like the DAP, turning “network budget” into incumbent subsidy.
    Who bears it: passive DOT holders via dilution or misallocation, and builders via higher political costs to access funding or favorable parameters.
    Measurable indicators: delegate vote share concentration by track, recurring treasury recipients, and growth of governance-controlled balances relative to security spend.

  2. Security budget fragility during the issuance transition.
    Trigger: stepped issuance reductions (first on March 14, 2026) coincide with validator cost pressure or falling DOT price.
    Mechanism: if validator economics deteriorate faster than fee-based or other revenue mechanisms mature, validator set quality can degrade, increasing tail-risk events (downtime, correlated failures, governance instability).
    Who bears it: users and builders first (liveness and reliability), then DOT holders (credibility and valuation).
    Measurable indicators: validator count stability, commission levels, and churn around the issuance step-down schedule.

  3. Coretime market mispricing and adversarial blockspace accumulation.
    Trigger: bulk coretime auctions clear at persistently low prices or are cornered by a small number of buyers.
    Mechanism: cheap coretime can subsidize builders at DOT holders’ expense (via insufficient burn to offset issuance), while cornering can raise barriers, reduce competition, and push legitimate teams into secondary markets.
    Who bears it: DOT holders (weak burn-driven sink), smaller builders (access costs), and users (reduced diversity of rollups).
    Measurable indicators: distribution of region ownership, secondary-market spreads, and the ratio of coretime burn to annual issuance.

Dominant risk: governance-controlled fiscal expansion without measurable ROI

This is the big one because it is the easiest way for a well-intentioned system to become extractive.

Polkadot structurally routes meaningful value into governance-controlled accounts. The treasury receives 80% of transaction fees and 15% of annual inflation. The DAP roadmap recap for March 2026 indicates an additional direction: stopping treasury burns and redirecting those tokens and slashes to the DAP. Meanwhile, coretime revenue is designed to be burned, explicitly to make “prices paid clearly costs” and to avoid distorted incentives.

Put those together and you get a political economy with two competing value narratives:

(1) Collective value accrual through burn mechanisms tied to adoption, like coretime revenue burns.
(2) Directed growth through treasury and DAP spending, decided by OpenGov tracks and turnout dynamics.

When (2) dominates (1), you can end up with a system where the token is primarily a political instrument funding a large set of ecosystem claimants. That can still “grow the ecosystem.” It can also devolve into a grants-and-marketing treadmill where the marginal recipient’s incentive is to lobby governance, not to build sustainable fee-paying demand for coretime or real user activity that justifies security spend.

The incentive-alignment test is simple and harsh: does a DOT-denominated outflow create measurable DOT-denominated inflow pressure later?

Coretime burn has a crisp answer. More demand means more burn. Treasury and DAP spending does not, unless governance enforces discipline with hard KPIs and credible clawbacks. Polkadot’s documentation is detailed on how funds flow in and how proposals pass. It is naturally thinner on enforceable ROI measurement, because that is a social problem more than a protocol problem.

The stepped issuance reductions beginning March 14, 2026 raise the stakes. If governance keeps large, loosely justified budgets while the security budget tightens, the system may respond by politicizing validator economics, changing slashing rules, or engineering new “revenue narratives” that are functionally dilution in disguise.

Polkadot can handle this risk. But only if OpenGov behaves like a credible monetary and fiscal authority, not like a permanently open payout queue.

If you are building a DOT-adjacent model, or designing an application economy around coretime costs, you should treat governance as a first-class parameter. This is the part where a tokenomics advisor earns their keep: scenario design, sensitivity analysis, and incentive audits that assume parameters will change. If you need hands-on support, our tokenomics design services can help you tie every subsidy to an observable behavior that increases paid demand for blockspace over time.



This article is part of our Tokenomics Deep Dive series.