How Polkadot Treasury Proposals Are Evaluated: Public On-Chain Votes and Review Standards

I have spent enough time reading Polkadot OpenGov threads to recognize the shape of this argument before it starts. A team submits a Treasury proposal, a bold comment appears calling itself a systemic risk audit, and the debate quickly stops being about one proposal and starts being about who is allowed to judge the work at all. That is exactly what happened around Referendum #1956, the ComputeFlux Pilot, when a comment titled “SYSTEMIC RISK AUDIT REPORT” recommended a hard NAY vote.

The poster behind the thread, writing on October 26, 2026, does not dispute the right of anyone to question Treasury spending. The challenge is narrower and, in my view, more important: who authors these assessments, what methodology they use, whether they examine public source code and deployed infrastructure before issuing conclusions, and whether there is any process for correcting factual inaccuracies. The post notes that ComputeFlux points to open-source infrastructure, Polkadot PVM smart contracts, an existing product, and a commercial business model, and argues that those claims were overlooked in the audit-style comment.

Key Metrics at a Glance

Three Eras of Treasury Review

The thread reads like a postmortem of Polkadot’s governance evolution. The poster describes an earlier period when a broad community actively evaluated Treasury proposals, mistakes and all, with wide distribution of responsibility and independent scrutiny. Then came the delegate-vote era, which the poster admits was part of, with its own errors, conflicts of interest, and inefficiencies. The claim is not that the past was perfect; it is that today meaningful evaluation appears concentrated in the hands of one or two entities, which triggers a vicious cycle: fewer independent reviewers participate, less scrutiny happens, and the remaining gatekeepers gain more influence over what gets funded.

Evaluator Accountability Score

Before treating any assessment as decisive, I would score the evaluator, not just the proposal:

The Steward Question

A sharper part of the argument concerns the steward role. The intended function was to help the ecosystem coordinate and make better decisions; the fear is that the steward became an owner of the system, an ultimate gatekeeper of funding, and an authority whose judgment substitutes for collective community intelligence. That framing matters because a vote can look decentralized on the surface while substantive decisions were already made behind the scenes. The poster’s standard is simple and worth repeating: the same standards must apply to every team, every foundation, every service provider, and every proposal.

Why Builders Disengage

The real cost of concentrated evaluation is not one questionable funding decision. It is the gradual exit of experienced builders and independent contributors. If reviewers cannot meaningfully challenge the dominant assessment, why should they invest time in governance? They will not, at least not seriously or for long.

What DOT Holders Should Ask

• Who authored the assessment, and how are they funded?
• Did the reviewer examine the public repository and deployed contracts, or only screenshots and headlines?
• Are potential relationships with proposal facilitators disclosed?
• Is there a public process to correct factual errors?
• Does the process reward independent analysis or only ratify gatekeeper conclusions?

TL;DR

• What: Around Referendum #1956 (ComputeFlux Pilot), a “SYSTEMIC RISK AUDIT REPORT” comment recommended a hard NAY, prompting a broader debate about who evaluates Treasury proposals.
• Why: The thread argues that meaningful evaluation has become concentrated in one or two entities, creating a cycle of less independent scrutiny and more gatekeeper influence.
• Impact: If independent reviewers stop participating, OpenGov risks looking decentralized while substantive decisions are made by a small group.
• Watch: Published methodologies, direct code review, conflict-of-interest disclosure, formal correction channels, and steward independence.

Sources

• Polkadot Forum: Who Evaluates Polkadot Treasury Proposals? Transparency, Technical Accuracy, and Supporting Real Builders

Gemma Nguyen is TotesTek’s Content Lead & Journalist, covering cryptocurrency, Web3, DeFi, blockchain technology, and emerging tech trends.