Help

Account creation

Account creation deploys a new onchain account through the Aragon app on the chosen network, ready for governance to be installed afterwards through the governance designer.

Entry points

  1. Reach out to the Aragon team — the preferred route for help planning deployment and governance. Aragon offers paid governance advisory and workshops, as well as deployment services for configurations that require the team.
  2. Self-serve from the Explore page — the app's landing page, which shows other accounts that have launched.

Self-serve deployment needs a connected wallet. Connecting through the wallet-connection modal requires accepting the Terms of Service and Privacy Policy.

Create account page

Self-serve creation

The flow is a two-step, no-code full-screen wizard, deliberately decoupled from governance design: the account publishes onchain before any governance detail is decided.

  1. Select chain. Choose a supported chain with account creation available. The chain is the parent deployment context: the account, and contracts later created for it such as a new governance token, belong to that chain. The picker separates Mainnets and Testnets, with Ethereum Sepolia selected by default. Choose Show all testnets to reveal the other test networks; Show fewer collapses the list while keeping the selected testnet visible.
  2. Define the account. Provide its name, logo, description, and resources. This metadata is posted to IPFS and later drives how the account is named and presented in the app (account presentation). On Ethereum mainnet this step also offers an optional <label>.dao.eth subname; when chosen, the factory assigns it during registration (the account's optional dao.eth subname).

Continuing from metadata opens the shared transaction dialog. It prepares and submits one deployment transaction through the OSx DAO factory. The resulting account has the admin plugin installed by default (decision), which puts it into the admin flow.

The new account is an OSx DAO whose factory bootstrap leaves ROOT with the account itself; its admin can execute actions immediately through the Admin governance. Guided creation and audited contracts do not establish that later governance choices are sound. Review the configuration choices that remain your responsibility before assigning authority or committing assets.

Last updated on

On this page