RADIX WikiRADIX Wiki

The DAO's rulebook is ratified as a package, in one Constitutional vote, so the entity has a working framework from the day it is formed. Since the April RFC rounds closed, that package has been named and counted: twenty-one documents, ratified by a proposal that does not itself form the entity or start the DAO.

Where it stands (19 August 2026)

The ratification proposal now exists as a document, and the operative governance repository — last updated 16 August 2026 — sets out what it ratifies and what it does not. It is numbered GP-PRE-1, Constitutional Ratification of the Governance Framework, and its status is "Ready for review (pre-formation)": written, not yet submitted, with no vote date set.

It is not the founding vote. It is the first of three. Under the Operating Agreement the framework is adopted through a sequence of community acts rather than a single ballot, and the repository states the sequence:

  1. GP-PRE-1 — Constitutional Ratification, taken before the entity exists, on the community's own governance system. It fixes the version of the framework the rest of the sequence proceeds on and satisfies Operating Agreement Schedule 5, condition 6.
  2. Formation. The Transition RAC files the Certificate of Formation and the Operating Agreement. The company exists and is member-managed; the Advisory Governance Period begins.
  3. GP-ELECT-1 — Permanent RAC election (Schedule 5, condition 7). At least five members must be elected and formally seated, each having completed KYC first, and the Transition RAC must open the election within 90 days of ratification so it cannot be stalled.
  4. GP-ACTIVATE-1 — the Activation Vote. On passage it sets the Activation Date: the company becomes Algorithmically Governed, governance outcomes become binding, and the Transition RAC sunsets.

The consequence is the part worth reading twice. Between formation and the Activation Date, community governance is advisory. The DAO exists, it is managed by its members, and a vote that passes in that window obliges the Transition RAC to acknowledge and explain rather than to execute — a recognised advisory outcome needs ≥7% participation and ≥50% YES to trigger even that duty. Only GP-ACTIVATE-1 closes the gap. Of the three, only GP-PRE-1 has been drafted; GP-ELECT-1 and GP-ACTIVATE-1 are marked draft scaffolds.

What GP-PRE-1 ratifies

Twenty-one documents: the Charter as the governance constitution, and twenty operational policies. In order — DAO Parameters Registry; Proposal & Voting Framework; Execution & Treasury Actions Policy; Emergency & Safeguards Policy; Treasury Signers Rules; On-Chain Identifiers & Verification Policy; RAC Mandate; Delegate Mandate; Conflict of Interest Policy; Code of Conduct; Compliance Operations Policy; Governance Maintenance & Upgrade Framework; Working Group Framework; Elections & Role Governance Policy; Governance Continuity Framework; Dispute Resolution & Arbitration Policy; Contributor Compensation Policy; Contributor Onboarding and Offboarding; Source Code Stewardship Policy; and the Open Source & Intellectual Property Policy.

That list supersedes the ten-document Phase 1 package the April RFC rounds discussed, and two documents named there do not appear in it: the Authorized Signers Rules is now the Treasury Signers Rules, and the Legal Wrapper & Representation document has no counterpart in the ratified set — the Operating Agreement does that work, and it is executed and filed by the Transition RAC rather than ratified by the community. The Roles Registry is explicitly excluded as a navigation aid.

The repository also fixes precedence, which decides what wins when two documents disagree: Marshall Islands law and the Certificate of Formation, then the Operating Agreement, then the Charter, then the operational policies, and the Parameters Registry inside that last tier. The Charter is written to survive a change of jurisdiction — if the DAO ever redomiciles, it travels with the community and a new legal wrapper recognises it.

The passing conditions, restated from the registry

GP-PRE-1 and GP-ACTIVATE-1 both carry Constitutional-level conditions: ≥66% YES against decisive votes, and a 10% quorum. A third test applies that the earlier reading of this card did not carry — minimum affirmative support of 3.5% of eligible voting power (registry §3.3A), because ABSTAIN counts toward quorum but not toward approval, and without a floor a proposal could be carried over the line largely by abstentions. All three tests must be met.

The base of that 10% is not the total XRD supply. The registry measures quorum against eligible voting power at the voting snapshot (§3.2), and §8A enumerates the sources: liquid XRD and LSUs converted to their XRD equivalent form an entrenched constitutional floor that no proposal can remove, and LSULP, fungible LP pool units on Ociswap, CaviarNine and DefiPlaza, Ociswap precision pools and CaviarNine shape pools sit in a second tier the RAC can adjust on 30 days' notice. Staked XRD therefore counts. The corollary drawn from the August total-supply reading — that XRD unable to reach the app raises the bar for everyone else — does not follow from the registry's definition. Delegation is recognised by Charter §5 but records as not yet enabled, pending platform support.

One further detail distinguishes this vote from every other the DAO will hold: no body determines its result. Because it is taken before the company exists, §3A.1 makes the outcome arithmetical, read from the public record of the system the vote ran on and published ministerially — the Proposal & Voting Framework's result-determination rule (§6.5) governs every vote except this one.

Deliverables

  • Community review of each Phase 1 document across the Round 1–4 RFC threads. Rounds 1–4 closed 23 April 2026.
  • Consolidate Rounds 1–4 into a single ratification proposal. Done — GP-PRE-1, drafted and ready for review.
  • Submit GP-PRE-1 and open the vote; no submission or vote date is published.
  • Draft GP-ELECT-1 and GP-ACTIVATE-1 past scaffold stage.
  • Publish which deployment the vote runs on — the DAO-dedicated Consultation instance at vote.radixdao.org, or the older consultation.mountain-top.live that ran the first three votes.
  • Record the ratified versions in the operative repository as the canonical baseline; the original repo is now a reference library.

Dependencies & cross-references

Sources

Where it stands (8 September 2026)

The section above is the position on 19 August and is kept as the record of it. Three things have moved since. GP-PRE-1 opened its Discussion phase on 30 August 2026 and lost its closing date on 2 September. The operative repository moved off a personal account on 29 August. And on 6 September 2026 the ratifiable text was amended for the first time since it was signed. The amendments are real, dated and public. They are not in the repository the DAO moved the framework into.

The amendments of 6 September

Two posts in the ratification discussion set out what changed. At 21:04 UTC Daffy reported a treasury change across five documents: the Single Transaction Limit of $12,000 USDC stands and splitting an obligation to fit under it stays forbidden, so a payment that genuinely is one payment now needs a Large Milestone Authorization instead, carried at ≥66% YES, executed at the 4-of-5 high-risk threshold after a 72-hour delay and only once delivery is verified. His summary of it is that the bar goes up, not the limit. Fifteen minutes later he answered a contributor review: seven of thirteen points incorporated, four declined as already covered by the text, and one, the Roles Registry giving the RAC a power the Proposal & Voting Framework gives the electorate, called the best catch in the batch.

That second post is also the one that says where the fixes are, and it is precise. Two were in an open PR. Three were on a follow-up branch. Both statements were true of Shadaffy/radix-dao-governance, the personal repository, at the minute he wrote them: its pull request #1 was opened at 20:57:53 UTC and merged at 21:25:50, six minutes after the post, and the three follow-up commits landed four seconds after that. The repository was pushed at 21:30:49 UTC, and the commit at the head of master trues up the dates on eight amended documents: the Parameters Registry, Treasury Signers Rules, Execution & Treasury Actions, Contributor Compensation, On-Chain Identifiers, Governance Continuity, Working Group Framework and Source Code Stewardship.

The DAO's own copy is not the amended one

The repository under the DAO's own organisation, RadixDAO/governance-framework, has received none of it. Read on 8 September 2026 its main is at commit 14a0510a of 27 August 2026, 13:25:05 UTC, whose message is that it records the SHA-256 hashes of the signed PDFs in the GP-PRE-1 manifest. It holds five commits in total. It has two branches, main and ratification-preparation, and they point at the same commit. Its pull-request list is empty for every state: no pull request has ever been opened there, so the one Daffy pointed readers to is not a pull request in the repository they would have gone to.

Compared file by file at the two head commits, 26 of the 30 documents present in both differ. Four are byte-identical: the Charter Reading Guide, the Policy Library Reading Guide, the Election Methods Guide and the Operating Agreement. The personal repository also carries GP-ELECT-1 and GP-ACTIVATE-1, the second and third of the three binding votes described above, which the organisation's copy does not contain at all.

Three of the differences are worth reading, because each is a rule rather than a wording preference.

  • Who can be overridden. Execution & Treasury Actions §5.3 in the organisation's copy reads that where the RAC determines that a refusal is invalid it may instruct remaining signers to proceed with execution directly, and stops there. The personal copy narrows the first half to a refusal grounded in Treasury Signers Rules §9, adds that a mandatory refusal under Treasury Signers Rules §8.2 is not subject to this paragraph, and defines the second half: the instruction bypasses the refusing or unresponsive signer, not the signing threshold. On the organisation's text, the council's override still reaches a refusal a signer is obliged to make.
  • Who picks the election method. The Roles Registry in the organisation's copy still reads that the election mechanism is selected by the RAC when it creates the election. That is the contradiction with Proposal & Voting Framework §4.5 that Daffy reported fixed.
  • When the patch clock starts. Source Code Stewardship in the organisation's copy says only that the RAC acknowledges receipt within 48 hours and assesses severity within 7 days. The personal copy adds a 48-hour assessment where a report indicates Critical severity on its face, and states that the patch timelines run from receipt of the report. The Critical patch window is 72 hours, and on the organisation's text nothing says when it begins. That is not an abstract question for a network that has committed no round since 31 August.

The divergence does not run one way, which is why neither copy can simply be adopted over the other. The Charter and the Proposal & Voting Framework are dated 27 August in the organisation's copy and 25 August in the personal one, and it is the organisation's copy that carries the manifest recording the hashes of the signed PDFs. The two also disagree about their own format: one stamps a version and date in an italic line, the other in a table row.

What that means for the vote

GP-PRE-1 ratifies a set of documents by manifest, and the manifest lives in the organisation's repository against hashes of PDFs signed to the 27 August text. Daffy's own note on the treasury change says the signed PDFs will be updated and resigned before Temperature Check, so the divergence is understood on his side and has a stated remedy. It is not yet public, and until it is, a reader following the Transition RAC's instruction on 7 September to check it out arrives at the unamended set.

The Official Venue has not closed the gap either. Read at 11:13 UTC on 8 September 2026, the notices feed holds the same two items it has held since 29 August, and its Process notices category is still empty. Nine days after the Discussion phase opened, the venue the framework designates for official acts has recorded neither its opening, nor its extension, nor the first amendments to the text it is about.

HydrateLast updated 1d agov2.1.07 revisionsVerified Sep 8, 2026