Polkadot's OpenGov: On-Chain Governance Explained

Polkadot's OpenGov is an on-chain governance system that lets DOT holders vote directly on proposals across dozens of parallel "tracks" — separate voting lanes for different categories of decisions, from small treasury spends to major protocol upgrades — replacing an earlier model built around a small elected council making most decisions on the community's behalf.

Governance on a blockchain determines how the protocol itself changes over time: which software upgrades ship, how a shared treasury is spent, and who has influence over those decisions. Polkadot's approach is one of the more elaborate on-chain governance systems in the industry, designed to let many proposals move through the system simultaneously rather than forcing everything through a single periodic vote.

How tracks work

OpenGov organizes every type of decision into a specific track — for example, a "root" track for the most fundamental protocol changes, a "treasurer" track for spending from Polkadot's community treasury, and various tracks for smaller technical or parameter changes. Each track has its own approval and support thresholds, its own voting period, and its own minimum deposit requirements, calibrated to the significance of the decisions that track handles. A minor parameter tweak moves through a lighter-weight track with lower thresholds; a fundamental change to the protocol's core logic requires a much higher bar to pass.

This design lets Polkadot process many proposals continuously and in parallel, rather than bottlenecking everything through infrequent, all-at-once votes the way some earlier blockchain governance systems worked.

Voting and delegation

DOT holders can vote directly on any proposal in any track, with their voting power generally weighted by the size and lock-up duration of the DOT they commit — locking DOT for longer periods increases voting weight, a mechanism intended to favor holders with genuine long-term commitment to the network over short-term speculation. Holders who don't want to actively track every proposal can delegate their voting power to another account they trust, on a per-track basis — meaning you could delegate technical tracks to a specific expert while retaining direct control over treasury votes, for instance.

What OpenGov actually decides

OpenGov proposals cover a wide range of protocol decisions: software upgrades and runtime changes, treasury spending on ecosystem grants and infrastructure, adjustments to Agile Coretime parameters (see our DOT token explainer for how coretime bonding works), and changes to the governance system itself. Because the system is designed to be continuous rather than periodic, protocol parameters can change relatively frequently compared to blockchains with rarer, more consolidated governance events.

OpenGov vs. other on-chain governance models

Feature	Polkadot OpenGov	Typical single-track on-chain governance
Parallel tracks	Many, calibrated by decision significance	Usually one general voting process
Delegation granularity	Per-track	Usually all-or-nothing
Voting power	Stake plus lock-up duration ("conviction")	Usually simple stake-weighted
Pace of change	Continuous, many proposals in flight	Often periodic, batched votes

Risks to understand

Stake-weighted, conviction-based voting systems like OpenGov can still concentrate real influence among large, long-term-committed holders and validators, even with delegation available to smaller holders — a common critique of on-chain governance broadly, not unique to Polkadot. Because OpenGov moves relatively continuously, low overall voter turnout on any given proposal can let a small, organized group swing a decision that affects the whole network — staying informed matters more here than on chains with rarer governance events. As always, verify you're using official Polkadot governance interfaces before submitting votes or delegating voting power, since governance and staking dashboards are common phishing targets given the high-value approvals involved; see our wallet security guide.

Bottom line

OpenGov gives DOT holders a genuinely more granular and continuous say in Polkadot's evolution than simpler governance models, through parallel tracks calibrated to decision significance and flexible per-track delegation. That granularity is a real strength, but it also demands more active engagement to avoid ceding influence to whoever shows up to vote — passive holders should understand what delegation options exist rather than simply ignoring governance altogether.