---
title: "Treasury WG · Stand up the treasury multisig & Authorized Signers"
url: "https://radix.wiki/ideas/dao-treasury-multisig-signers"
version: "1.1.0"
updated: 2026-08-16
license: CC-BY-4.0
license_url: "https://creativecommons.org/licenses/by/4.0/"
---

# Treasury WG · Stand up the treasury multisig & Authorized Signers

| Status | 🟠 Proposed |
| --- | --- |
| Working Group | Treasury & Finance WG |
| Category | ⚖️ Governance |
| Governance Phase | Phase 1 – active at launch |
| Champion | Peachy · StakingCoins |
| Origin | [Governance tools thread](https://radixtalk.com/t/governance-tools-and-processes-needed/2119) · [Authorized Signers Rules](https://radixtalk.com/t/rfc-dao-governance-framework-reference-repo/2268) |

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](https://dashboard.radixdlt.com/account/account_rdx1c9l27suy4nte9ymge5c3eqqnnfepgf9p28d9lcsv3jvmd0f0z8j2fx) 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](https://github.com/Shadaffy/radix-dao-governance/blob/master/pending/parameters/dao-parameters-registry.md) 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](https://dashboard.radixdlt.com/transaction/txid_rdx1kg65rh9spggn32h0cqj5d7jyn8n07euv98cmcj05xryn6rt5u4vqrgzjdg) 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](/contents/tech/core-concepts/radix-governance#on-chain-register).

## 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

- Governed by [Daffy's Radix DAO framework](https://github.com/Shadaffy/radix-dao) (repo `Shadaffy/radix-dao`); see the [Governance Framework Reference Repo](https://radixtalk.com/t/rfc-dao-governance-framework-reference-repo/2268) and [Charter (Round 1)](https://radixtalk.com/t/rfc-dao-documents-round1-the-charter/2269).
- Depends on [DUNA incorporation](/ideas/dao-incorporate-duna-llc).
- Spends against [operating budgets](/ideas/dao-operating-budgets); stores assets per [XRD custody](/ideas/dao-xrd-custody).

## Sources

- [Governance tools and processes needed (Treasury/Multisig app)](https://radixtalk.com/t/governance-tools-and-processes-needed/2119)
- [Reference repo – Execution & Treasury Actions Policy](https://radixtalk.com/t/rfc-dao-governance-framework-reference-repo/2268)