This page carries the operative text of the Radix DAO Charter verbatim, so it can be read and cited in one place. The text below is version 1.0.0, last updated 27 August 2026, taken from pending/constitutional/charter.md in the DAO’s operative governance repository, which moved to the RadixDAO organisation on 29 August 2026. It is not in force. It becomes the DAO’s constitution when the ratification vote described below passes.
The text this page carried until 26 August 2026
From 31 March to 26 August 2026 this page mirrored a different document: version 0.1.0, a draft adapted from the Aragon Network DAO Charter under CC-BY-SA-4.0. That draft left its own operative numbers unset. Its election clause gave a nomination period of [TBD] days, a discussion period of [TBD] days and a vote of [TBD] days, and term length, consecutive-term limits and removal thresholds were [TBD] as well. The v1.0.0 text below contains no placeholder anywhere. It is written for Radix rather than adapted from another DAO, it carries no Aragon lineage and no CC-BY-SA licence, and at 29,866 bytes it is roughly half the length of the draft it replaces.
The two texts sit in different repositories, and the project says plainly which one governs. Shadaffy/radix-dao is the reference library, holding every draft and every policy not yet activated, and it was last pushed on 7 May 2026. The operative repository is the one that moved: it was Shadaffy/radix-dao-governance on a personal account until 29 August 2026 and is now RadixDAO/governance-framework under the DAO's own organisation, updated only when a governance proposal passes. Most cards on this board still cite the reference library rather than either operative path.
How it is ratified: GP-PRE-1
The Charter is ratified by one named proposal, GP-PRE-1, Constitutional Ratification of the Governance Framework, authored by the Transition RAC and put to the community on its own consultation system, which the proposal called Consultation V2 on 25 August and calls Consultation V3 in the 29 August rewrite. It is a Constitutional proposal, so it needs 66% YES on a 10% quorum of eligible voting power. An abstention counts toward the quorum and is excluded from the approval calculation, and a separate floor applies underneath: YES votes must reach 3.5% of eligible voting power in their own right.
What the vote ratifies is not the Charter alone. Its manifest lists 21 documents at version 1.0.0: the Charter, and a twenty-document operational policy library covering the parameters registry, proposals and voting, treasury execution, emergencies, treasury signers, on-chain identifiers, the RAC and delegate mandates, conflicts of interest and conduct, compliance, governance upgrades, the Working Group framework, elections, continuity, disputes, contributor compensation, onboarding, source-code stewardship and intellectual property. Each is to be published to the Official Venue as a signed PDF, and the hash recorded against it is the SHA-256 of that PDF rather than of the markdown file. Read on 26 August 2026 every hash cell in the manifest read to be recorded at signing; read on 29 August all twenty-one carry a hash, and the proposal has dropped the submission-date field it had left to be confirmed.
Ratification is not activation
The framework is adopted through a sequence of four community acts rather than one founding vote, and the proposal history now names three of them:
- GP-PRE-1, framework ratification, taken before the company exists. Satisfies Activation Condition 6 of the Operating Agreement.
- Formation. The Transition RAC files the Certificate of Formation and the Operating Agreement. The company exists and is member-managed.
- GP-ELECT-1, the Permanent RAC election. Activation Condition 7, and a precondition of the fourth step.
- GP-ACTIVATE-1, the Activation Vote. Confirms every Activation Condition is met and sets the Activation Date.
The gap between the second step and the fourth is the part that surprises. Charter §4A.1 calls it the Advisory Governance Period: from formation to the Activation Date the company is member-managed and governance outcomes are advisory, and where an advisory outcome clears the recognition threshold the Transition RAC must publish an acknowledgement, or its reasons for declining to act. §4A.2 limits the community’s binding acts in that period to three, and they are the ratification, the election and the Activation Vote. Only on the Activation Date does the company become Algorithmically Governed, do governance outcomes bind it, and does the Transition RAC sunset (§4A.4).
Status as at 26 August 2026
Nothing has been ratified yet, and the repository layout says so without a word of commentary: in the operative repository the constitutional/, parameters/, governance/, legal/ and working-groups/ directories each hold a single empty .gitkeep, and every document named in the manifest sits under pending/. The Charter and GP-PRE-1 were last changed on 25 August 2026, in a commit titled a pre-ratification quality pass across the policy library.
The Transition RAC’s update of 13 August 2026 set the framing that still holds: the company existing is a necessity, and a Charter the community understands and uses is what governance rests on. Ratification runs in parallel with incorporation, its real dependency is the voting app rather than the text, and the seven-seat election cannot open until the Charter is ratified, because the ratified rulebook is where that election’s process and conditions live. No date is fixed for the vote.
See Radix Accountability Council for the council itself, and Radix governance for where the Charter sits in the wider framework.
Signed and staged (29 August 2026)
Three days after the reading above, the framework was signed and the repository holding it moved. The Transition RAC announced on 29 August 2026 that the community's governance repository now sits with the RadixDAO GitHub organisation as RadixDAO/governance-framework, and asked readers to adjust their links to it. The old path is not a redirect: Shadaffy/radix-dao-governance still resolves, still carries the 25 August text, and was last pushed on 25 August 2026, so a citation left pointing at it now quotes a superseded version rather than breaking.
GP-PRE-1 was rewritten in the move, from 15,396 bytes to 8,068, and the rewrite is where the substance is. The proposal now opens with a header naming its thresholds by parameter reference, and its manifest carries a SHA-256 for every one of the twenty-one documents rather than the placeholder each cell held on 26 August. A new section §2A identifies the key those signatures chain to – a single self-signed certificate created by the Transition RAC, serial 497dc3092ebc024f6350b92a77fa14790de75b03, SHA-256 fingerprint 73B1D38C5F4137307ADDEE4F8AF8BB922F887739C9FD9E499CFEAE10DACDE92D – and states that a document whose signature chains to any other certificate is not a ratified version whatever its hash. The certificate is published on its own so that it can be checked against a signature independently.
Behind the manifest sit the documents themselves. pending/signed/ holds twenty-three signed PDFs: the twenty-one ratifiable documents, plus the two instruments the community does not vote on – the Operating Agreement and the Non-Profit DAO LLC Certificate of Formation, the latter dated 13 August 2026 at v1.02. Signed is not filed and neither is ratified. The Certificate of Formation is a document the Transition RAC has executed and has yet to lodge with the Marshall Islands; the same day's earlier update puts the MIDAO submission at Monday 31 August at the earliest, with four to six weeks for the registry to issue the certificate after that.
The repository layout is the status board, and it still reads pre-ratification. constitutional/, governance/, legal/, parameters/ and signed/ each hold nothing but a .gitkeep; everything in the manifest is under pending/. The repository README spells out what a YES vote physically does: each .md source moves from pending/ to its root category folder and each PDF moves from pending/signed/ to signed/, leaving the pending folders empty for the next cycle. Every merge to main is meant to correspond to a passed vote, which makes the commit history the audit trail.
The same announcement opened radixdao.org as the DAO's Official Venue – the term the Operating Agreement uses for the place a ratified document must be published to. Its Notices & Records section carries the first two entries, both dated 29 August 2026 and both signed PDFs: the certificate details above at 15:07 UTC, and the minute of the Transition RAC's 25 August meeting at 16:41 UTC, which records the decisions that enable the ratification process. The site banner states the phase in one line: Phase 1 · Pre-formation. Ratification vote pending. Community decisions are advisory until activation. No date has been set for the vote itself; the RAC says only that it opens with a discussion period supported by a new RadixTalk topic.
The Discussion phase opens (30 August 2026)
The day after the framework was signed and staged, the process to adopt it started. The Transition RAC announced at 17:30 UTC on 30 August 2026 that ratification of the Governance Framework is under way and that the Discussion phase runs for seven days from that moment. It is anchored at a single RadixTalk topic, Charter & Policies Ratification Discussion, opened twenty minutes earlier at 17:10 UTC and signed by the three named Transition RAC members, Tadkis, Mr. Peanutbutter and projectShift. The RAC asks that everything a reader thinks needs changing be raised in that thread — linking out is fine, but the objection has to be made where the record of the discussion is kept.
The vote itself has still not opened, and this is the distinction the card carried from 29 August: discussion is the first phase of the ratification process, not the ballot. What runs for seven days is scrutiny of the twenty-one documents; the binding GP-PRE-1 vote follows it, on the community's own Consultation V3 system, at thresholds unchanged from the ballot text — 66% YES of decisive votes, a 10% quorum, and a 3.5% affirmative floor.
What the discussion is asked to check
The RAC's explanatory post is unusually specific about the work it wants done, and about its own standing: the post "is explanatory and has no legal force", and "where this post and the ballot text differ, the ballot text governs". Within that, it asks for four things — verify the SHA-256 of each signed PDF against the manifest and flag any mismatch, compare the .md sources in the repository against the signed PDFs, challenge the sequencing if ratifying before formation is the wrong call, and point at anything reading as authority the RAC should not have.
One consequence of that framing is easy to miss and changes what a reader should cite. What is ratified is the signed PDF, and only the PDF is hashed in the manifest. The markdown in the repository is the working source the PDF was rendered from: it stays editable after the vote, nothing in the manifest pins it, and where the two differ the signed PDF governs. Every citation on this board that points at a .md file — including the Charter source in this page's own infobox — points at the convenient copy rather than the operative one.
The post also states the founding conflict plainly rather than leaving it to be found: the Transition RAC authored the framework it is asking the community to ratify. What it offers as mitigation is this discussion period, the community's ability to reject the proposal, and the fact that GP-PRE-1 confers no new authority on the RAC — the establishment mandate is pre-existing and unchanged by the vote.
The venue record lags the announcement
The framework's own rule is that a ratified document is published to the Official Venue, and the venue keeps a machine-readable record of what has officially happened. Read at 19:10 UTC on 30 August 2026 — an hour and forty minutes after the announcement — its JSON feed carries exactly two items, both dated 29 August: the certificate details and the minute of the 25 August meeting. The venue's Process notices category exists and holds nothing, and the site banner still reads Ratification vote pending. Community decisions are advisory until activation, with the body text beneath it saying the first vote "has not been called".
None of that is wrong: the vote has not been called, and the RAC has not claimed the Discussion phase is a notice. It does mean the opening of the process is recorded on Telegram and on a forum, and not yet in the record the framework designates for it. The governance repository reads the same way — its last commit is 27 August, the manifest-hash commit, and every document named in the manifest is still under pending/.
The clock is removed (2 September 2026)
The Discussion phase opened with a deadline and, three days in, no longer has one. At 13:49 UTC on 2 September 2026 the Transition RAC published a status update, signed as the earlier ones were by projectShift, saying that with the network halted there are no technical conditions to proceed to a Temperature Check or beyond, and that it had therefore decided to keep the Discussion phase open for as long as it is needed, regardless of the initially set 7 days
. The seven-day window announced on 30 August would have closed on 6 September 2026. It has no closing date now.
The council put the same decision where it had asked readers to look. The anchor topic Charter & Policies Ratification Discussion carries the change in its own first post, which now reads that the phase stays open regardless of the initially set period
. So the forum and the Telegram channel agree, and the RAC's argument for the extension is that scrutiny of the framework is the one useful thing left available while the ledger is stopped.
The DAO's own record still does not say it. Read at 15:08 UTC on 2 September, the Official Venue's notices feed holds the same two items it has held since 29 August, the certificate details and the minute of the 25 August meeting, and its Process notices category is still empty. Four days after the phase opened the venue the framework designates for official acts has recorded neither its opening nor its extension. That is the same gap this page recorded on 30 August, now larger.
What the first three days of discussion produced
The extension is worth measuring against the participation it extends. Read at 15:10 UTC on 2 September, three days after it opened, the anchor topic holds 13 posts from four accounts and has been viewed 151 times. Eight of the thirteen were written by projectShift, the Transition RAC member who opened it: the council that authored the twenty-one documents has written more of the thread scrutinising them than everyone else combined. The other three participants are Magal36, with three posts, one of which withdraws its own point as out of scope, and skywave and dazligth with one each.
The substance of what was raised is narrow. Magal36 asked on 30 August for direct links to the signed PDFs and a way to verify a signature, and was told to use the repository rather than a list of individual links; skywave asked on 31 August how many people sit on the pre-DAO RAC, and was told five, of whom three are named on the ratification posts. The first submission that engages the text at length arrived on 2 September at 12:47 UTC, from dazligth, and the RAC's reply an hour later says it will take time to address. GP-PRE-1 asks the community to verify twenty-one document hashes, compare each signed PDF against its markdown source, and challenge the sequencing. Three days in, none of that work is visible in the thread.
# Radix DAO Charter
*Version v1.0.0 — Last updated 2026-08-27*
---
## 1. Purpose
The Radix DAO ("the DAO") was established to ensure that the Radix ecosystem is governed by those who have a stake in its future — its community of token holders — rather than any single organisation or authority.
The DAO's mission encompasses:
* Education and research in decentralized ledger technology and its applications
* Development and management of blockchain protocols, distributed systems, and open-source cryptographic software
* Advancement of cryptographic systems for public benefit
* Governance of decentralized networks and protocols
The DAO exists to:
* Steward and allocate resources for the long-term benefit of the Radix ecosystem
* Enable genuine decentralized governance by token holders
* Support the sustainability, security, and growth of the network through accountable, community-led decision-making
The DAO may receive assets from external contributors and shall manage those assets in strict alignment with this purpose.
---
## 2. Nature of the DAO
The DAO is a **community-governed coordination system**. It does not replace the need for human judgment, expertise, or good faith — it organises them. Authority rests with the community, expressed through defined governance processes and delegated to execution bodies that remain accountable to it at all times.
The DAO operates through:
* Token-holder governance
* Defined governance processes
* Delegated execution and oversight bodies
This Charter defines the DAO's principles and authority.
---
## 3. Core Principles
The DAO is governed by seven principles. These are not aspirations — they are binding commitments that shape every governance decision and constrain every actor within the system.
### 3.1 Decentralization
Authority ultimately resides with the community of token holders. No individual, body, or organisation holds permanent power over the DAO's decisions or resources. Delegated authority exists only to serve efficiency and execution — it does not transfer sovereignty.
---
### 3.2 Transparency
Governance actions must be publicly visible and auditable. The community can only hold the DAO to account if it can see what is happening and why. Temporary confidentiality is permitted only where necessary to mitigate security risks, prevent exploitation, or fulfill legal or contractual obligations — and all such actions must be disclosed retrospectively.
---
### 3.3 Accountability
All use of DAO-controlled resources must be accountable to the community. Those entrusted with authority — whether elected, appointed, or contracted — are stewards of the community's trust, not owners of it. Accountability mechanisms are not optional features; they are core to the legitimacy of every action taken in the DAO's name.
---
### 3.4 Stewardship
The DAO manages resources to benefit the ecosystem and its future participants. Resources are not held for their own sake — they exist to be deployed purposefully, in service of a network that is intended to endure.
---
### 3.5 Resilience
The DAO must remain operational under all circumstances, including failure of governance bodies, resignation of representatives, or technical and coordination disruptions. No single point of failure should be able to halt the DAO's ability to govern.
Resilience does not preclude lawful dissolution of the DAO where approved in accordance with the Charter, Operating Agreement, and applicable governance procedures.
---
### 3.6 Integrity
All participants are expected to act in good faith. Disclosure and recusal obligations apply only to individuals holding formal roles with delegated or elevated decision-making authority. The integrity of governance depends not only on rules, but on the character of those who participate in it.
---
### 3.7 Environmental Responsibility
The DAO is mindful of environmental impact. Where reasonably practicable and without compromising mission effectiveness, the DAO may consider energy efficiency and sustainability in its decisions.
---
## 4. Governance Authority
### 4.1 Token Holder Sovereignty
Token holders are the ultimate decision-making authority of the DAO, supreme over every body and office it creates. This sovereignty is the DAO's foundational constitutional principle. It is exercised through, and bounded by, this Charter: it does not extend to outcomes that this Charter places beyond amendment (§12.1), nor to outcomes that exceed the authority recognised by the Operating Agreement and Marshall Islands law (§13). Within those bounds, all governance power flows from and returns to the community. A purported governance outcome that breaches an Entrenched Provision (§12.1) is void and acquires no legal effect; declining to execute such an outcome enforces this Charter and does not derogate from token-holder sovereignty. The point at which valid governance outcomes acquire **binding legal effect** on the Company is governed by the Operating Agreement: during the Advisory Governance Period (from formation to the Activation Date) governance outcomes are advisory under **Operating Agreement §§5.8–5.9**, save for the three binding community acts identified in §4A; from the Activation Date, validly determined governance outcomes are binding decisions of the Company under **Operating Agreement §5.7**.
---
### 4.2 Established Bodies
The DAO may establish chartered bodies, including:
* Accountability Council (RAC) — constituted as the Transition RAC during the Transition Period and as the Permanent RAC thereafter
* Working Groups
* Committees
Such bodies operate within defined mandates, remain subordinate to DAO governance at all times, and may be removed or replaced by DAO vote. Establishing such bodies is a matter of operational necessity, not a transfer of authority.
The DAO's operational functions are performed by **Delegates**, whose Delegated Functions and mandate are defined in the **Delegate Mandate**. A Delegated Function is seated by allocation by the Accountability Council from among its seated members, or by election under the **Elections & Role Governance Policy** where the DAO has so resolved by Governance Proposal. Under either route the holder exercises no authority beyond the function conferred and remains removable by the DAO. The Delegate framework is established as operational and delegated functions under **Operating Agreement §11.5**; the **Legal Signatory** Delegated Function maps onto the Legal Signatory recognised in **Operating Agreement §1.15 and §9.2**. Legal Membership in the LLC attaches to the Delegated Functions defined in the Delegate Mandate and to seats on the Accountability Council.
Legal Membership in the LLC is constituted under **Operating Agreement Article IV** and is a compliance structure separate from Governance Participation, which is exercised by Governance Participants through the Governance Mechanism under **Operating Agreement Article V** (taking binding legal effect in accordance with §4.1 of this Charter).
---
### 4.3 Binding Decisions
Governance-approved decisions, once they have binding legal effect in accordance with §4.1, are binding on the Company and executed through the Governance Mechanism and authorized execution entities (Treasury Signers, multisig custody). Prior to the Activation Date, governance outcomes other than the three binding community acts in §4A are advisory only (**Operating Agreement §§5.8–5.9**), and the Transition RAC must have regard to them but is not bound by them.
---
## 4A. Activation and the Advisory Governance Period
The Company is **member-managed during the Transition Period** and becomes **Algorithmically Governed** only on the Activation Date, when the Activation Vote passes (**Operating Agreement Article VIII**). This section establishes the constitutional framework for that transition; the detailed mechanics and parameters are carried by the operational policies named below, which form part of the DAO's governance framework.
### 4A.1 The Advisory Governance Period
From the date of formation to the Activation Date, governance outcomes produced through the Governance Mechanism are **advisory** (**Operating Agreement §5.8**). Where an advisory outcome meets the recognition thresholds specified in the **DAO Parameters Registry**, the Transition RAC must, within the period specified in the **RAC Mandate**, publish an acknowledgement to the Official Venue and, where it declines to act, its reasons (**Operating Agreement §5.9**).
### 4A.2 The three binding community acts
The community's binding acts are limited to the three below. The first precedes formation; the second and third fall within the Transition Period, which commences on formation (**Operating Agreement §1.21**).
1. **Framework ratification** — the constitutional ratification of this Charter and the full policy framework, at the ratification threshold for constitutional matters specified in the **DAO Parameters Registry §3A.1** (**Operating Agreement Schedule 5, condition 6**; and see §4A.2A);
2. **The Permanent RAC election** — conducted under this Charter and the **Elections & Role Governance Policy**, with the seat minimum, KYC-before-seating, and fixed election timing specified there (**Operating Agreement §7.1 and Schedule 5, condition 7**); and
3. **The Activation Vote** — the sole binding governance vote of the Advisory Governance Period, whose voting period, quorum, majority, and failure handling are specified in the **DAO Parameters Registry §3A.2** (**Operating Agreement §§1.4, 8.6**).
### 4A.2A Ratification precedes the Company
Framework ratification is a community act taken before the Company exists and is not an exercise of authority under the Operating Agreement. It fixes the version of this Charter and the policy framework on which the founding sequence proceeds.
It is recognised twice: on formation — by the Company's ratification and adoption of the vote and its record on execution of the Operating Agreement (**Operating Agreement §11.1A**) and by the Transition RAC's unanimous written resolution (**Operating Agreement Schedule 5, condition 6(a)**) — and by the **Activation Vote**, which in confirming the Activation Conditions recognises the ratification, the formation, and the Transition RAC's completed tasks.
The version ratified is the version that binds. Recognition confers no power to alter it (**Operating Agreement §11.1A**); amendment before the Activation Date is made under §12 or §12.2 of this Charter, subject always to the amendment rules of the Operating Agreement — the transition thresholds and protected-matter rules to which **Operating Agreement §§11.1A and 12.1(a)** subject such amendments, including the protected-matter rule in **Operating Agreement §9.12(e)** and, where an Entrenched Provision is engaged, the elevated threshold in **Operating Agreement §12.2(c)**.
### 4A.3 Activation Conditions
The Activation Conditions are set out in **Operating Agreement Schedule 5** and may be supplemented by conditions specified in this Charter and the policy framework.
The handover conditions referred to in **Operating Agreement §8.4(h)** and Schedule 5 (condition 10) are those specified in the **Operating Agreement** — the implementation of the handover to the Permanent RAC and the long-term governance framework under **§6.5(h)**, and the residual handover steps preserved by **§6.10** — together with any specified in this Charter. This Charter specifies no additional handover condition.
### 4A.4 Effect of Activation
On the Activation Date the Company becomes Algorithmically Governed, governance outcomes validly determined through the Governance Mechanism become binding decisions of the Company (**Operating Agreement §§5.7, 8.8**), the Transition RAC sunsets (**Operating Agreement §6.10**), and the Permanent RAC assumes its constitutional role (**Operating Agreement Article VII**).
---
## 5. Governance System
The DAO operates through a governance system consisting of proposal submission, community deliberation, voting, and execution. Token holders may participate directly or by delegating their voting power to a representative of their choosing.
Funds under the DAO's control may not be used for governance participation. No balance in an account the DAO controls may be voted, delegated, or used to file or support any governance action. This rule determines who may vote; it does not change how quorum is measured.
---
## 6. Treasury Stewardship
The DAO maintains and allocates treasury resources to support the Radix ecosystem. Treasury use must align with the DAO's purpose, and all significant allocation decisions require governance approval.
The treasury is deployed through two principal mechanisms: compensation for contributors working on behalf of the DAO, and grants to external projects and teams building on the Radix network. Both represent an investment in the ecosystem's future.
---
## 6A. On-Chain Identifiers and Verification
The DAO operates on public infrastructure, and the identifiers through which its governance and treasury operate must themselves be public. The governance smart contracts, the treasury accounts, and the resources that constitute eligible voting power shall be recorded in an authoritative register that is published to the Official Venue and independently verifiable by any person against the on-chain data.
The register, the rules for how each identifier is configured and used, and the means of verification are carried by the **On-Chain Identifiers & Verification Policy**, which forms part of the DAO's governance framework. That policy is the operational record referred to in **Operating Agreement §11.4**; this Charter establishes the principle of public, verifiable on-chain identifiers, and the policy governs its implementation. No identifier may be relied upon in governance before it has been recorded and made publicly verifiable in accordance with that policy.
---
## 7. Governance Safeguards
The DAO maintains mechanisms to prevent harmful or malicious actions, resolve disputes, and respond to emergencies. These are not extraordinary measures — they are a permanent and necessary part of a governance system that operates in public, with real assets, and at scale.
The DAO also provides structured channels for reporting governance integrity violations by those in positions of authority. No role in the DAO is above accountability.
---
## 8. Governance Integrity
The DAO maintains an Accountability Council (RAC) to ensure that governance processes are followed and decisions are executed correctly. The RAC acts as a guardian of process — not a decision-making authority — and operates within a strictly defined mandate.
During the Transition Period, the RAC is constituted as the **Transition RAC** under Operating Agreement Article VI, with a narrow formation mandate (**Operating Agreement §6.5**) that cannot override governance: during the Advisory Governance Period the community's governance outcomes are advisory (§4A.1), so no override arises. Following the Transition Period, the RAC is constituted as the **Permanent RAC** under **Operating Agreement Article VII** — the standing governance-process oversight body of the Company. The Permanent RAC is the guardian of the governance process and constitutional order and is not, unless expressly stated otherwise, a manager, general executive, treasury-management, or policy-making authority (**Operating Agreement §§7.2–7.3**). Its composition, candidacy rules, election mechanics, term, removal, and reporting obligations are governed by this Charter and the **Elections & Role Governance Policy** and **RAC Mandate** (**Operating Agreement §7.4**).
All persons holding formal roles with delegated or elevated decision-making authority are subject to disclosure and recusal obligations. Governance Participants exercising ordinary governance voting rights are not subject to mandatory disclosure or recusal, but are encouraged to act in the DAO's best interest.
---
## 9. Continuity and Fallback
The DAO must remain operable under all circumstances. In the event of governance failure, authority reverts to token holders and emergency mechanisms enable the restoration of normal governance.
Continuity mechanisms apply only while the DAO remains active. They do not override or prevent lawful dissolution processes defined in the Operating Agreement.
The DAO also maintains standards for the security review of any smart contracts or on-chain systems it governs. Technical deployments must not outpace the community's ability to assess and authorise them.
---
## 10. Non-Distribution Principle
The DAO's assets and income exist to advance its purpose — not to enrich its participants. All resources must be applied to the benefit of the Radix ecosystem. No distributions may be made to Governance Participants, Members, or Delegates except as expressly permitted under the non-distribution principle and permitted payments in **Operating Agreement §§3.4–3.5**.
This principle is not merely a legal constraint. It is a statement of intent: the DAO is a steward, not a vehicle for extraction.
---
## 11. Asset Lock and Wind-Down
Should the DAO ever be dissolved, its remaining assets must be transferred to an entity with substantially similar objectives. No assets may be distributed to token holders, Governance Participants, Members, or Delegates upon dissolution.
This is a binding constitutional commitment. The DAO's resources were entrusted to it for the benefit of the Radix ecosystem; that purpose does not end with the DAO's existence.
The mechanics of dissolution — including the asset lock, successor entity criteria, and the application of property on winding up — are governed by **Operating Agreement Article XIII**. This Charter establishes the principle; the Operating Agreement governs its execution.
---
## 12. Amendments
This Charter may be amended through DAO governance using a Constitutional proposal. It is a living document — it should evolve as the DAO matures — but changes to it require the highest level of community deliberation and approval.
Amendment procedures and document versioning requirements are defined in the **Governance Maintenance & Upgrade Framework**. Where a proposed amendment to this Charter would amend, or take effect as an amendment to, a provision that is an Entrenched Provision under **Operating Agreement §12.2(a)** — including any provision of this Charter designated as an Entrenched Provision and recognised as such in the Operating Agreement — it may be made only in accordance with the elevated Entrenched-Provision amendment thresholds in **Operating Agreement §12.2(c)** (during the Transition Period) or **§12.2(d)** (following the Activation Date), in addition to the requirements of this section.
### 12.1 Entrenched Provisions
Notwithstanding the above, the following provisions may not be amended, reduced, or removed by any governance proposal, regardless of approval level:
1. **The Non-Distribution Principle (§10) and Asset Lock (§11)** — these provisions exist to satisfy the DAO's legal obligations as a non-profit entity under Marshall Islands law and may not be weakened by any governance vote.
2. **Minimum Constitutional quorum floor** — the quorum threshold for Constitutional proposals may not be reduced below **7%** of eligible voting power by any proposal, including a Constitutional proposal. Any proposal purporting to do so is void and may not be executed.
3. **Governance sovereignty constraint** — no governance proposal may grant any body or person unilateral authority to override a valid DAO vote outcome or permanently alter governance rules without a subsequent community approval process.
4. **Minimum voting power source floor** — XRD (liquid holdings) and LSU (Liquid Staking Units, converted to XRD-equivalent at snapshot) shall always be recognised as eligible voting power sources for all DAO governance votes. This floor may not be reduced or removed by any proposal, including a Constitutional proposal.
The two governance floors above (the **7% Constitutional quorum floor**, item 2, and the **XRD+LSU voting-source floor**, item 4) are also designated as Entrenched Provisions in the Operating Agreement itself (**Operating Agreement §12.2(a)(ix)–(x)**), so they carry Operating-Agreement-level entrenchment in addition to the Charter-level entrenchment in this section.
---
### 12.2 Emergency Amendments
Because this Charter is superior to the operational policy library (§13), a power to amend this Charter in an emergency must be established by the Charter itself and cannot be conferred by an operational policy alone. This section establishes that power. The **Governance Maintenance & Upgrade Framework §9** and the **Emergency & Safeguards Policy** carry its operational detail and are subordinate to this section.
Notwithstanding the standard amendment process in §12, where an emergency requires a temporary amendment to a document in the policy framework — this Charter or an operational policy — before that process can complete, the amendment may be adopted by **unanimous written consent of all Delegates**, subject to ratification by Governance Proposal within 30 days. An emergency amendment that is not ratified within 30 days is void and of no effect from the expiry of that period.
During the Transition Period, when the Delegated Functions are held by the Transition RAC (Delegate Mandate §6; **Operating Agreement Article VI**), "unanimous written consent of all Delegates" means the unanimous written consent of all seated Transition RAC members, and the ratification requirement is satisfied by a recognised advisory outcome meeting the standard recognition thresholds (**DAO Parameters §3A.3**).
This power is strictly limited. An emergency amendment:
1. may amend only this Charter or an operational policy, and may not amend, vary, or suspend the Operating Agreement, the Certificate of Formation, or any other Formation Document;
2. may not amend, weaken, reduce, or remove any Entrenched Provision (§12.1), and may not alter the Activation framework (§4A);
3. takes effect only as a temporary measure pending ratification and confers no authority to make a permanent change without the ratifying Governance Proposal required by this section, consistent with the governance-sovereignty constraint (§12.1 item 3);
4. must be publicly disclosed on adoption in accordance with the Transparency principle (§3.2); and
5. confers no protection on actions taken in reliance on it if ratification fails: where an emergency amendment is not ratified, any action taken under it that would not have been valid under the unamended document must be reported and reviewed under the **Emergency & Safeguards Policy §10**, and any treasury disbursement so made is recoverable by the Company unless separately ratified by Governance Proposal; and
6. does not authorise, before ratification, the **seating of a person in a role**, a change to the **treasury signer set or its thresholds**, or a transfer or exercise of the **Master Badge, the Owner Badge, or the Governance Operations function**. Unlike a disbursement under item 5, these cannot be undone (**Emergency & Safeguards Policy §10**) — and an exercise of the Master Badge is the least undoable of them, since it can mint, recall, or invalidate the Owner Badge itself.
For the purposes of this section, "written consent" has the meaning given in the **Emergency & Safeguards Policy**.
---
## 13. Scope
This Charter is the DAO's governance constitution. It contains the principles, structural authority, and entrenched provisions that the community has adopted to govern itself. It is designed to remain stable across legal jurisdictions — adopted by the community independently of any particular legal wrapper, and recognized by whichever legal entity the community uses to give its decisions legal effect.
Within the Marshall Islands legal structure, this Charter is incorporated by reference into the Operating Agreement and given legal effect by it. The Operating Agreement is the Company's primary legal instrument; this Charter is the DAO's governance constitution. The two documents are designed to work together, with the following hierarchy:
- **Marshall Islands law and the Certificate of Formation** are supreme by operation of law. This Charter does not and cannot override any mandatory provision of Marshall Islands law or the Company's Certificate of Formation.
- **The Operating Agreement** is the Company's primary legal instrument and prevails over this Charter in the event of conflict. This Charter and all operational policies derive their legal force from the recognition given to them in the Operating Agreement.
- **This Charter** is subordinate to the Operating Agreement but prevails over all operational policies. Where this Charter and an operational policy conflict, this Charter prevails.
- **All operational policies** are subordinate to both the Operating Agreement and this Charter. A provision of an operational policy that conflicts with this Charter or the Operating Agreement is void to the extent of the conflict.
This hierarchy is intentional. The Operating Agreement is the legally registered instrument that courts, regulators, and counterparties look to; it must be supreme in legal terms. This Charter is the document that the community has agreed binds it as a constitutional matter. The Operating Agreement gives the Charter legal effect and recognizes its authority over the operational policy library, while reserving statutory and registration matters to itself.
Operational, technical, and procedural details are defined in the DAO's policy library — a set of governance documents that give effect to the principles and authority established here.
**The policy library forms part of this Charter.** The policy library ratified by the community together with this Charter forms part of this Charter for the purposes of the Operating Agreement — including **Operating Agreement §11.1**, which requires the Charter to contain the DAO's detailed governance framework, the candidacy, nomination and election rules for the Permanent RAC, and its detailed governance process mechanics; and the references in **Operating Agreement §1.19** and **Schedule 5, condition 7** to the Elections Policy "forming part" of the Charter. The documents so incorporated are those listed in the ratification proposal that adopts this framework. In particular, the **Proposal & Voting Framework**, the **Elections & Role Governance Policy**, the **DAO Parameters Registry**, the **RAC Mandate**, and the **Delegate Mandate** carry the governance process mechanics, election rules, and role definitions that Operating Agreement §11.1 locates in the Charter.
Incorporation does not alter the order of precedence set out above: the Operating Agreement continues to prevail over this Charter and over every incorporated policy, and this Charter continues to prevail over every incorporated policy where they conflict. Nor does it alter the amendment route for an incorporated policy, which remains a Governance Process proposal under the **Governance Maintenance & Upgrade Framework** — except where a change would amend this Charter itself or an Entrenched Provision, in which case §12 applies.
**Document Activation:** This Charter and the policy framework are ratified by the community through the constitutional ratification vote that forms part of the Activation Conditions (**Operating Agreement Schedule 5, condition 6**), and are recognised and given legal effect by the Operating Agreement as the governance framework of the Company. The Transition Period, defined in **Operating Agreement §1.21 and Article VI**, is a formation period during which a Transition RAC implements entity formation, asset transfer, the constitution of the Permanent RAC, and handover. During that period the Company is **member-managed** and governance outcomes are advisory (§4A.1); **full algorithmic governance under this Charter and the subordinate governance rules recognised under Operating Agreement §§11.2 and 11.5 begins on the Activation Date** (**Operating Agreement §§8.1, 8.8**), not at formation.
---
## 14. Notices and Service
This section establishes the DAO's constitutional framework for notices and service. The Operating Agreement governs the statutory and registration role of the Registered Agent (**Operating Agreement §2.4**); this Charter establishes the principle, and the **Compliance Operations Policy §5** carries the operational procedure and is subordinate to this section.
**Legal notices to the Company** — including service of process, regulatory correspondence, and formal legal demands — are served at the address of the Registered Agent identified under **Operating Agreement §2.4**.
**Internal governance notices** — including proposals, disclosures, advisory acknowledgements, and announcements to Members and Governance Participants — are validly given by publication to the **Official Venue** (**Operating Agreement §1.18**).
Any legal notice, demand, order, or regulatory correspondence received at the Registered Agent must be **forwarded to the Delegates and disclosed to the community** by publication of notice of receipt to the Official Venue. The Compliance Operations Policy §5 carries the operational detail of this obligation, including the 48-hour forwarding-and-disclosure timeframe and the Regulatory Demand Disclosure Protocol.