RADIX WikiRADIX Wiki

Majority Judgment is a voting method in which each voter grades every candidate on one shared scale of words rather than ranking them or picking one. It was set out by Michel Balinski and Rida Laraki in A theory of measuring, electing, and ranking, published in the Proceedings of the National Academy of Sciences in May 2007.[1] The argument behind it is that a ballot asking who you prefer collects less information than a ballot asking how good each candidate is, and that a method counting grades can escape some of the failures that follow from counting preferences.

The Radix DAO governance framework adopts it as the default mechanism for every election the DAO holds, including the seven-seat Permanent Radix Accountability Council.[2] Radix implements one deliberate departure from the published method, and it is the detail this page exists to state plainly: the share of voting power that settles a candidate’s grade is three-fifths, not one half. Radix elections are not decided on the median grade.

How the count works

Every valid ballot assigns exactly one grade to every candidate on the list. A ballot that leaves any candidate ungraded is invalid and is not counted, and the Radix framework requires the ballot interface to refuse an incomplete submission at the point of casting, so that honest voter error cannot show up later as low turnout.[2] Each voter’s full voting power is applied to each grade that voter assigns. There is no Abstain grade: a voter who does not want to support a candidate grades them low, and the scale itself carries that.

Counting a candidate is one pass down the scale. Start at the highest grade and accumulate the voting power that placed the candidate at that grade or above. The first grade at which the running total reaches the required share is the candidate’s qualifying grade. Under the published method that share is one half and the result is the candidate’s median grade, which Balinski and Laraki call the majority grade. Under the Radix framework the share is three-fifths, which is why the result is not a median and the framework does not call it one.

Because every valid ballot grades every candidate, the voting power measured is identical for every candidate in the round. Qualifying grades are therefore directly comparable, and no candidate can be flattered by having been graded on fewer ballots than a rival.

The Radix variant, term by term

Four settings do the work, and three of them live in the framework text rather than in the parameter registry, which means changing them is an amendment rather than a parameter change.[3]

TermValueWhat it does
Grade scaleExcellent, Very Good, Good, Acceptable, PoorFive ordered grades. The order is normative; the implementation indices 4 down to 0 encode the order and are never averaged
Grade QuantileThree-fifths, fixed in the framework, not a parameterThe share of voting power cast that must place a candidate at or above a grade for that grade to be theirs
Minimum Qualifying GradeGoodThe lowest qualifying grade at which a candidate may be seated at all. A ranking alone does not seat someone the electorate grades below the floor
Quorum7% of eligible voting powerParticipation needed for the round to count, unchanged on the single permitted rerun

The quantile is set to three-fifths so that it matches the 60% approval threshold the DAO’s other election mechanism applies per candidate, putting the same share-of-turnout test to a candidate whichever mechanism is in force.[3] The two settings are not independent of one another: raising the quantile lowers every qualifying grade computed on the same ballots, so a floor left unchanged silently becomes a higher bar.

Radix also resolves an exact split upward where some of the literature resolves it downward. Where the running total arrives at exactly three-fifths at a grade, that grade is the qualifying grade, so a candidate graded Excellent by exactly three-fifths of the voting power cast and Poor by the rest qualifies at Excellent. The framework gives its reason: the rule follows from a single accumulation pass and can be checked against the published tallies without a second rule.[2]

Ties, and what a low turnout buys

Candidates are ranked by qualifying grade, and that ranking is itself the seating order, so there is no separate confirmation round of the kind the two-stage mechanism needs. Where two candidates share a qualifying grade and the tie decides a seat, it is broken by the majority gauge: for each tied candidate, compare the share of voting power that graded them above their qualifying grade against the share that graded them below it. The framework applies the gauge rather than the iterative middlemost-grade formulation, on the stated ground that the gauge is computed in one pass over the published tallies and can be verified by any member from the result.[2]

A round that closes below quorum may be re-run exactly once, and the rerun is deliberately not made easier: same quorum, same quantile, same electability floor, same snapshot of the electorate, with double the voting period. The framework spells out why, and the reasoning is worth reading whatever one thinks of the method. A rerun on lower thresholds is a different question rather than more time to answer the same one, and a reduced quorum would make the rerun cheaper to control than the round it exists to rescue, which is an incentive to suppress turnout in the first round.[2] If the rerun also closes below quorum, no candidate is elected and every seat is referred to vacancy handling.

The mechanism is on the ledger, and has never run

Majority Judgment is not only drafted. The governance component the framework routes through is deployed on Radix mainnet, running blueprint Governance v1.0.0, and among its nineteen methods is vote_on_majority_judgment_election. Its stored state holds a majority_judgment_elections key-value store alongside temperature_checks and proposals, each with its own counter.[4] Read from the ledger repeatedly through August 2026, all three counters read 0. The contract the whole framework depends on is live and has processed nothing, which is the correct state while nothing in the framework is yet operative.

Two things stand between the method and its first use. Ratification of the Governance Framework is an activation condition of the DAO’s Operating Agreement and needs a vote, and the network halt that began on 31 August 2026 stopped the ledger a vote would have to run on. The council responded by removing the seven-day limit on the discussion phase and leaving it open-ended, so the first Radix election held under Majority Judgment has no date.

One further caution for anyone reading the deployed contract against the written rules. The component’s election parameter set carries a field named minimum_median_grade, and the framework it implements settles grades at the Grade Quantile and not at the median. The name is a leftover from an earlier reading; the framework text is the authority on what the field means.

See also

References

  1. ↑ Michel Balinski and Rida Laraki, “A theory of measuring, electing, and ranking”, PNAS 104(21):8720, 22 May 2007 β†—
  2. ↑ RadixDAO governance-framework – Proposal & Voting Framework, sections 4.5, 6.2.4, 6.3 and 6.5 β†—
  3. ↑ RadixDAO governance-framework – DAO Parameters Registry, sections 3.5 and 6B β†—
  4. ↑ Radix Dashboard – the deployed Governance v1.0.0 component, read at epoch 338,958 on 28 August 2026 β†—
HydrateLast updated 1d agov1.0.01 revision