Hey everyone,
I want to kick off a real conversation about where Polkadot’s governance stands right now and where it’s headed. Launching OpenGov was a huge milestone for us, a real technical leap. The whole idea was to give the community real, on-chain democracy through Conviction Voting.
Now that we’re seeing how it actually works out in the wild, it’s a good moment to step back and ask: is our governance setup really as decentralized as we hoped? Sure, the tools are there, but honestly, some things seem to be pulling decision-making back toward the center, maybe more than we intended.
Here’s what I’ve noticed, and a few ideas for how we might keep moving toward true community control.
- Voting Weight Is Lopsided
Lately, the Web3 Foundation (W3F) has been voting in OpenGov referenda using a big chunk of its original genesis tokens. I get why, they want to protect the network and make sure the treasury is handled responsibly, especially right now while things are still settling. But let’s be real: when one group holds that much voting power, it throws things off balance.
If W3F’s weight comes mostly from those early allocations, not tokens bought on the open market, it tips the scales. It’s easy for that kind of weight to outweigh everyone else, from individual holders to big funds and validators.
- How This Affects People Actually Using the Network
For OpenGov to work the way it’s supposed to, everyone, from the smallest DOT holder to the biggest, needs to feel that their vote really counts.
If a single group can basically decide the outcome of any referendum, that’s going to put people off. Why bother participating or locking up tokens when the result feels predetermined?
And for validators, the folks running the backbone of the network, tracks like the Root are critical. If voting power is stacked too heavily in these areas, it messes with confidence in network neutrality and future rules.
- Who’s Actually Steering Development?
Right now, W3F holds most of the funding, and Parity Technologies does most of the core development. That means the same people who pay for the work also have the deciding vote on what gets built, thanks to their voting power in OpenGov.
If we want a healthier, more transparent ecosystem, maybe it’s time to rethink how we fund development and who approves it.
- Where Do We Go From Here?
If we really want Polkadot to live up to its Web3 promise and stay strong for the long haul, we need to consider some changes. Here are four ideas for the community to chew on:
W3F as an Advisory Board: Imagine if W3F stepped back from voting with its TGE funds. Instead of making the final calls, it could focus on giving technical advice, audits, and research, guiding the community, but not controlling decisions.
Direct Treasury Funding: What if core dev teams, including Parity, pitched their roadmaps straight to OpenGov? Funding would come directly from the on-chain treasury, not from W3F. That way, developers answer to the community, not just a single entity.
Encourage Multiple Development Teams: Polkadot only gets stronger if we have more than one team building core software. If we separate funding from one central source, we can support independent teams to build alternative clients. That means more competition, more innovation, and better reliability, just like other big networks do.
Move Genesis Funds Into the Treasury: We could gradually shift W3F’s original DOT holdings into the on-chain treasury. These funds would be set aside for core development and big strategic projects, with the community in charge of how they get used.
Polkadot’s tech is second to none. If we can get our governance to match the quality of our code, there’s nothing stopping us.
I’m really looking forward to hearing your thoughts. Let’s keep this discussion open and positive, and see how we can take the next big step together.