Quadratic Voting: When It Actually Makes Sense

Quadratic voting is a scheme where each additional vote on the same option costs more than the last, so buying ten votes for one choice costs a hundred credits, not ten. The point is to let people say how strongly they feel, not just which side they are on. It is a genuinely good idea for a narrow set of decisions, and a bad fit for most. If your problem is that a passionate minority keeps getting steamrolled by a mildly-preferring majority, quadratic voting helps. If your problem is Sybil attacks or contested outcomes, it does nothing, and it might make things worse.

What quadratic voting actually does

In plain one-person-one-vote, everyone gets one vote per issue and intensity is invisible. Someone who would be ruined by a decision has exactly as much say as someone who mildly dislikes it. Quadratic voting fixes that by giving each voter a budget of credits they can spread across issues, where the cost of votes on a single issue rises with the square of the number of votes. One vote costs one, two votes cost four, three cost nine.

The math forces a real tradeoff. To pile votes onto the thing you care about most, you spend down your budget fast, so you have to genuinely prioritize. The result is meant to surface intensity of preference across a whole slate of decisions, which a plain count throws away.

When quadratic voting is the right tool

Reach for it when three things are true.

You have a budget of decisions, not one binary. Quadratic voting shines when voters allocate across many funding proposals or priorities at once. Public-goods funding rounds use it well: each backer spreads credits across projects, and the square-cost makes them concentrate only where they truly care.

Intensity matters more than headcount. If a decision genuinely harms a few and mildly pleases many, a plain majority produces a bad outcome. Quadratic voting gives the harmed minority a way to spend hard against it.

Your roster is already solid. This is the catch that sinks most deployments. Quadratic voting assumes one budget per person. If someone can split into ten identities, they get ten budgets, and the square-cost that was supposed to bound their influence collapses. Sybil resistance is a precondition, not a nice-to-have.

When it quietly fails

Do not use quadratic voting for a simple yes or no with a clean electorate. It adds cognitive load and buys you nothing. People understand "vote for A or B." They do not intuit credit budgets, and confused voters produce noisy results.

It also fails under collusion. If voters can coordinate or sell their credits, the intensity signal becomes a market for influence, which is just vote buying wearing a nicer coat. And it does nothing for disputed outcomes: quadratic voting is about how preferences are weighed, not about whether the result can be trusted or resolved.

The honest failure mode is complexity theater. Teams adopt quadratic voting because it sounds sophisticated, ship it for decisions that never needed it, and end up with lower turnout and a mechanism nobody understands. That is a downgrade dressed as innovation.

How to run it without fooling yourself

If you decide it fits, do a few things. Publish the credit budget and the cost curve before voting opens so nobody can claim they were surprised. Log every allocation so the count is auditable later. Lock the roster to a snapshot so budgets cannot be manufactured mid-vote. And explain the mechanic in one screen, with an example, or your turnout craters.

On MintVote I treat quadratic voting as one mode among several, not the default, because most community decisions are better served by a plain verifiable count. The right question is never "what is the most clever mechanism." It is "what does this decision actually need." Quadratic voting is a precision instrument for allocating a budget across many priorities among a known, Sybil-resistant electorate. Use it there and it earns its keep. Bolt it onto a simple vote and you have added friction to buy a signal you did not need.