RADIX WikiRADIX Wiki

Execution is separated from decision-making: an M-of-N multisig holds DAO funds and Authorized Signers move them only against an approved proposal – "No RFP = No Payment!". Signers are selected via RFC/RFP with fixed term limits; non-signers get read-only visibility.

Where it stands (August 2026)

The multisig is deployed, and it is 2-of-3. The primary multi-signature treasury account recorded in the framework's On-Chain Identifiers & Verification Policy on 11 August 2026 carries an owner rule of CountOf(2) over three Ed25519 signature badges, read on 16 August 2026 at epoch 335598. That matches the document exactly: DAO Parameters §6A specifies 2-of-3 for ordinary actions in this phase, rising to 3-of-5 standard and 4-of-5 high-risk on the Activation Date.

It has moved something. On 13 August 2026 the Consultations Master Badge was deposited into it, the first governance authority the account has held; it otherwise holds 200 XRD from a 10 August funding transaction. What the deployment does not yet carry is the process around it. The Authorized Signers Rules are unratified, so terms, rotation and revocation bind nobody; the mandatory RFP-reference field is a convention no on-ledger rule enforces, and the badge deposit carried no message; and the read-only visibility promised to non-signers is, for now, the public account address itself. Cross-referenced on Radix Governance.

Deliverables

  • Deploy an on-ledger M-of-N multisig (a shared Scrypto blueprint was offered by StakingCoins).
  • Ratify the Authorized Signers Rules (selection, 1-year terms, rotation, revocation).
  • Enforce a mandatory RFP-reference field on every outgoing transfer (XRD and USDC).
  • Provide read-only treasury dashboards for the community.

Dependencies & cross-references

Sources

HydrateLast updated 4d agov1.1.03 revisions