--- title: "How to Start a DAO on Radix" url: "https://radix.wiki/contents/resources/how-to-start-a-dao-on-radix" updated: 2026-10-17 license: CC-BY-4.0 license_url: "https://creativecommons.org/licenses/by/4.0/" version: "1.0.0" --- # How to Start a DAO on Radix | DAO tools on Radix, read 17 October 2026 | | | --- | --- | | On mainnet | [CrumbsUp](/ecosystem/crumbsup), dormant | | On the test network only | [Caper](/ecosystem/caper), on Stokenet | | Interface paused | [Muan Protocol](/ecosystem/muan-protocol), waiting on its V2 | | Build your own | [Scrypto](/contents/tech/core-protocols/scrypto-programming-language) with [badges](/contents/tech/core-concepts/badges) and [access rules](/contents/tech/core-concepts/access-rules-and-auth-zones) | | Legal wrapper in use | Marshall Islands non-profit DAO LLC ([Radix DAO](/contents/tech/core-concepts/radix-governance)) | ## How do I start a DAO on Radix? You start a DAO on Radix either with a platform built for it or by writing your own components in Scrypto, Radix's Rust SDK. Read on 17 October 2026, three platforms exist: CrumbsUp runs on mainnet but has been idle for months, Caper runs only on Stokenet, the Radix test network, and Muan Protocol has taken its app offline while it prepares a new version. A DAO, or decentralized autonomous organization, is a group whose members decide by vote what happens to a shared treasury and to the contracts it controls. On Radix the vote and the treasury can be tied together without any key held by a person, because the authority to move assets is itself a token that a component can hold. This page lists the tools with their state and sets out the build-it-yourself route. ## Which DAO tools work on Radix today? - **CrumbsUp** is a platform for creating and running DAOs on mainnet. [crumbsup.io](https://www.crumbsup.io/) still serves its app, whose dApp definition is [a mainnet account](https://dashboard.radixdlt.com/account/account_rdx169dlzydn4f2pekcd2an2nj0506g9v7fytp9a4thkw6secy7zjt0zg2) that last transacted on 5 May 2026. The wiki rates the platform dormant: its [CrumbsUp page](/ecosystem/crumbsup) counted 21 DAOs, 11 proposals and 19 votes on the ledger on 30 August 2026, with no activity since April. - **Caper** creates member-owned organizations, each launched with its own token, a market for that token and a treasury its holders govern, which a member can leave with their share. It runs on Stokenet: [caper.network's](https://caper.network/) live feed links to Stokenet transactions, so its tokens and treasuries hold no value. [Caper](/ecosystem/caper) has the details. - **Muan Protocol**, built by the studio Sentura, is a governance and voting framework. [muanprotocol.com](https://muanprotocol.com/) serves a notice that the app is offline while the next version, built around snapshot voting, is prepared for mainnet, and that positions already on the ledger are unaffected. The site still presents the certificate that expired on 2 September 2026, so a browser shows a warning first. A [Stokenet instance](https://stokenet.muanprotocol.com/) still answers. None of the three is running DAOs with real assets at present, so a group that needs one now builds its own or waits. The [ecosystem directory](/ecosystem) lists each project's status as the wiki last read it. ## How do I build a DAO myself in Scrypto? You write a component that holds the DAO's treasury and the badges that guard everything else, and release them only when a vote passes. Scrypto [handles authorization with badges, access rules and roles](https://docs.radixdlt.com/docs/auth) instead of checking the caller's address: a protected method declares an access rule, and a call succeeds only if the caller's auth zone holds a proof that satisfies it. The documentation's own example is a component that holds a badge and produces proofs of it, which is the shape a DAO takes: the component, not a person, holds the badge, so the code that counts votes is the only thing that can present it. The pieces are covered on their own pages: [components](/contents/tech/core-concepts/components) and [blueprints](/contents/tech/core-concepts/blueprints-and-packages) for the code, [badges](/contents/tech/core-concepts/badges) and [access rules and auth zones](/contents/tech/core-concepts/access-rules-and-auth-zones) for permission, and the [advanced access rules](https://docs.radixdlt.com/docs/advanced-accessrules) documentation for rules that combine several badges or amounts. Test on [Stokenet](/contents/tech/releases/stokenet) first. The Radix DAO publishes [every governance contract, badge and treasury account it uses](https://radixdao.org/verify/) with links to check each on the Radix Dashboard, which makes it a working reference for how the parts fit together on mainnet. ## Does a DAO on Radix need a legal entity? Radix sets no requirement, and a DAO that holds only on-ledger assets can run without one. The network's own DAO chose one: [Radix DAO LLC](https://github.com/RadixDAO/governance-framework) is a non-profit DAO LLC under Marshall Islands law, which stays member-managed, with community votes advisory, until an activation vote makes its on-ledger governance binding. The [incorporation card](/ideas/dao-incorporate-duna-llc) records how the Radix DAO weighed its options. The Radix DAO governs the network's shared assets and is not a service for creating other DAOs. [Radix Governance](/contents/tech/core-concepts/radix-governance) covers how it works, and caper.network's [DAO governance concepts](https://caper.network/wiki/dao-governance/concepts) cover voting, treasury and membership design on any chain. ## External Links - [Authorization](https://docs.radixdlt.com/docs/auth) – Radix documentation for Scrypto - [radixdao.org](https://radixdao.org/) – the Radix DAO's proposals, votes and contract addresses - [RadixDAO/governance-framework](https://github.com/RadixDAO/governance-framework) – the Radix DAO's governance documents - [CrumbsUp](https://www.crumbsup.io/) · [Caper](https://caper.network/) · [Muan Protocol](https://muanprotocol.com/)