RADIX WikiRADIX Wiki

Every threshold the governance process depends on is centralised in one registry, so a parameter can be tuned by Governance Proposal without amending the Charter. The card asked the community to settle the opening values. They are settled and published — a single document of roughly 59,000 characters in the operative governance repository, and one of the twenty-one documents GP-PRE-1 ratifies. It sits in the operational-policy tier of the precedence stack, below the Operating Agreement and the Charter.

The settled values

Quorum (§3.2), measured as participation — YES + NO + ABSTAIN — against eligible voting power at the vote's snapshot: Constitutional 10%, Governance Process 7%, Treasury/Budget 7%, Executable 5%, Temperature Check 3%. Treasury and Budget proposals carry an additional absolute floor of 50 unique voting addresses, an abstention counting toward it, because the floor measures breadth rather than direction.

Approval (§3.3), measured as the YES share of decisive votes — YES + NO, excluding ABSTAIN: Constitutional ≥66%, Governance Process ≥60%, Treasury/Budget ≥50%, Executable ≥50%, Temperature Check ≥50%.

Minimum Affirmative Support (§3.3A) is the section with no counterpart in the Round 2 RFC this card was written from, and it closes a hole the two tests above leave open. Because ABSTAIN counts toward quorum but not toward approval, a proposal can in principle be carried over quorum largely by abstentions and then decided by a very small base of actual support. So a YES floor applies independently, as a share of eligible voting power: 3.5% Constitutional, 2% Governance Process, 1.5% Treasury/Budget, 1% Executable. Each figure is about half the YES share a zero-abstention vote clearing quorum at its approval threshold would produce, which is the same as saying abstentions may carry at most roughly half the participation burden. All three tests must pass.

Durations (§3.1): ≥5 days of draft discussion, a 5–7 day Temperature Check, a 5–7 day binding vote, and a 5-business-day window in which a passed Temperature Check must be elevated or documented grounds for delay recorded with the RAC — elapse without either arms an elevation backstop. Cooldowns (§3.4): 7 days after a failed proposal, none for a minor fix, and one Treasury proposal per wallet per rolling 30 days.

Eligible voting power (§8, §8A) answers the question a quorum percentage is meaningless without: a percentage of what. Liquid XRD and LSUs converted to their XRD equivalent at the snapshot are a constitutional floor, entrenched by Charter §12.1 item 4 and removable by nothing. A second tier the RAC can adjust on 30 days' notice holds LSULP, fungible LP pool units on Ociswap, CaviarNine and DefiPlaza, Ociswap precision pools and CaviarNine shape pools. Delegation is recognised by Charter §5 but the registry records it as not yet enabled, pending platform support — an implementation status, the document is careful to say, not a limit on the right.

Activation parameters (§3A) govern the founding sequence itself. Framework ratification and the Activation Vote both run at ≥66% YES on a 10% quorum with the 3.5% affirmative floor; the Permanent RAC election must open within 90 days of ratification and seat at least five KYC-verified members before the Activation Statement; and an advisory outcome during the pre-activation period needs ≥7% participation and ≥50% YES to be "recognised" at all, which is what obliges the Transition RAC to respond to it.

Deliverables

  • §3.1 voting durations · §3.2 quorum requirements · §3.3 approval thresholds · §3.4 cooldown periods. Published.
  • §4 veto parameters · §8 identity & participation parameters · §9 execution parameters. Published, alongside sections the RFC did not anticipate: §3A activation, §6A treasury signers, §6B elections, §6C dispute resolution, §9A continuity.
  • Classify each parameter as minor (patch) vs major (structural) for future amendments — §11 defers this to the Governance Maintenance & Upgrade Framework §4–6 rather than settling it in the registry.
  • Publish the registry as machine-readable config the governance app can read. Done on 12 August 2026, as five parameter sets on the DAO governance component – see below. The Markdown remains the normative text.

Dependencies & cross-references

Sources

The registry reaches the ledger (12 August 2026)

The last open deliverable on this card asked for the registry as machine-readable config the governance app can read, and noted that it remained prose in Markdown with nothing consuming it programmatically. That is no longer true. Between 17:23 and 17:33 UTC on 12 August 2026, five GovernanceParameterSet entries were written into the parameter_sets key-value store of the DAO's Radix DAO Consultations component, each by an owner-gated add_governance_parameter_set or update_governance_parameter_set call. Read live at epoch 337,473 on 23 August, all five are present and none is retired.

Parameter setLabelTemperature checkBinding stage
dao-constitutionalConstitutional5 days · 405,249,777 XRD · 50%7 days · 1,350,832,592 XRD · 66%
dao-governanceGovernance Process5 days · 405,249,777 XRD · 50%7 days · 945,582,814 XRD · 60%
dao-treasuryTreasury or Budget5 days · 405,249,777 XRD · 50%7 days · 945,582,814 XRD · 50%
defaultStandard Executable (version 2)5 days · 405,249,777 XRD · 50%7 days · 675,416,296 XRD · 50%
dao-electionMajority Judgement Election3 days · 405,249,777 XRD · 50%7 days · 945,582,814 XRD · median grade Good

The durations and the approval thresholds are §3.1 and §3.3 exactly: 66, 60, 50, 50, 50, on a five-to-seven-day temperature check and a seven-day binding vote. The quorums are §3.2 exactly too, but expressed differently, and the difference matters. Each is a fixed quantity of XRD rather than a percentage the contract computes at the snapshot, and the four distinct figures stand in a clean 10 : 7 : 5 : 3 ratio to a single base of 13,508,325,920 XRD. That base is not eligible voting power. XRD total supply read at the state version of the first of those five writes was 13,508,342,408.66 – the same number to within about half an hour of issuance – so the percentages were struck against total supply, while §3.2 defines quorum as participation against eligible voting power at the vote's snapshot and §8A defines that as a strict subset of supply: liquid XRD, LSUs, LSULP and eligible pool positions. Against the smaller base the same absolute figure is a larger share, so each threshold as deployed is harder to clear than the registry's own percentage reads. Nothing in the contract updates it, either: supply inflates by roughly 300 million XRD a year, so an untouched figure drifts downward as a share of supply and can only be corrected by an owner-gated update_governance_parameter_set call.

Two of the registry's tests are absent from the ledger entirely. StandardProposalParameters carries three fields – voting days, quorum, approval threshold – and has no room for the 50-unique-address floor on Treasury and Budget proposals, nor for §3.3A Minimum Affirmative Support, the independent YES floor of 3.5 / 2 / 1.5 / 1% that stops a proposal being carried over quorum by abstentions. Both remain off-ledger tests that whoever publishes a result must apply by hand, which is the same division of labour that already governs the tally itself: the ballots are on-ledger, the arithmetic that judges them is not. The dao-election set is the one entry with a different shape, and its terms are read out on the permanent RAC card.

HydrateLast updated Sep 1, 2026v2.1.15 revisionsVerified Sep 2, 2026