Governance WG · Elect the Permanent RAC

The current RAC is an explicitly time-bound Transition RAC. The DAO must elect a Permanent RAC to act as trustees who action the community's will – appointing contributors and agreeing contracts for marketing, business development, market making, and wallet/engine development. Community discussion frames the role as high-level (like a company board on a 6–12 month budget horizon), initially unpaid, with paid roles requiring a separate community vote.

Where it stands (August 2026)

Nominations opened before the process did. On 15 July 2026 Timan Rebel posted an RFP self-nominating for the permanent RAC, and several other community members put themselves forward in that thread and in a parallel volunteer delegate-candidate RFP carrying a business and finance remit. Both threads were still drawing replies at the end of July.

What did not exist was the machinery to hold the vote. The Consultation app instance in use through July handles temperature checks and proposals but not elections; the DAO-dedicated instance announced on 4 August is the first build extended to support them, by the same Timan Rebel standing as a candidate. That places this card behind the Constitutional Proposal in the queue, since the constitutional vote is the new instance's first job.

The 13 August 2026 RAC update

The Transition RAC's status update of 13 August 2026 settled three of this card's open parameters and left the fourth – a date – open. The council will seat seven members. At least seven people have already declared a willingness to stand, there is no cap on candidates, and the council encourages more to come forward on the grounds that a contested field is the point. The election cannot open until the Charter is ratified, because the Charter is where the election's process and conditions are set – so this card sits behind ratification, which in turn waits on Consultation V2. No date is attached to any of the three.

The ballot will use Majority Judgment, which the council confirms is being implemented into the Consultation dApp for this election. Every voter grades every candidate on one shared scale, and seats go by best median grade rather than by who is named on the most ballots. The Radix implementation pins that median to a stated fraction: under Proposal & Voting Framework §6.2.4 a candidate's grade is the highest one that three-fifths of the voting power cast placed them at or above, the same share-of-turnout test the framework's other mechanism applies at its approval threshold. Most of the electorate will not have met the method before, and the council asks candidates and voters to raise doubts about how it works ahead of the ballot rather than during it.

The mechanism is deployed and has never been run. The governance component the framework routes through carries a majority_judgment_elections key-value store with its own counter, and read live at epoch 334782 on 14 August 2026 that majority_judgment_election_count is 0, as are proposal_count and temperature_check_count. See Radix governance for how that component relates to the earlier Consultation instance the transition votes have actually run on.

Deliverables

• Agree council size and mandate (build on the 5-member approval-vote precedent; some argue 7).
• Run the election via the ratified RFC → TC → RFP process and the governance app.
• Define the boundary between "community will at a high level" and RAC operational discretion within approved budgets.
• Set conflict-of-interest and (un)paid-role rules before seating members.

Dependencies & cross-references

• Governed by Daffy's Radix DAO framework (repo Shadaffy/radix-dao); see the Governance Framework Reference Repo and Charter (Round 1).
• Seats the body that holds interim RFP authority until Working Groups activate.
• Governance context: Radix Governance hub.

Sources

• Radix DLT Official – DAO/RAC discussion (2026-07-11)
• RDD structure & no-confidence mechanics