Aragon CLI Setup Guide

As a DAO Admin, the aragonCLI is your best friend. The CLI unlocks a whole world of possibilities that are simply not available in the UI. From installing new Apps to interacting with DeFi protocols. In this guide, we will walk through installing and setting up the Aragon CLI on Ubuntu 19.04, but this should work on any Debian based distro.

0. Update system

First things first update and upgrade your system.

sudo apt-get update && sudo apt-get upgrade

1. Install dependencies

build-essential , git , & python are all required for the CLI to install. we will use curl to install NVM in the next step.

sudo apt install build-essential git python curl

2. Install NVM

NVM enables you to install several versions of NodeJS on your machine. even if you will only have one version installed at any time, it is still useful to use NVM to have Aragon CLI sandboxed on that version. I f you use zsh or another shell, replace bash at the end of the command with the name of the shell you are using.

curl -o- | bash

Once installed open a new terminal window and enter.

nvm install 12.15.0

3. Install Aragon CLI

We are ready to install the CLI. Install the Aragon CLI globally with:

npm i -g @aragon/cli

If that was successful you should be to install IPFS with the command.

aragon ipfs install

4. Setup CLI

For you to submit any transactions to the network, the CLI will need a key to sign transactions with. there are two ways to do this. First (and recommended way to interact with the CLI) is with Frame. Frame is an OS level signing provider that allows you to interact with the CLI on any network and using your hardware wallet. Frame also has a smart account feature which enables you to sign transactions on behalf of your DAOs Agent (before putting them to a vote if you don’t have unilateral permissions to do so)

The second way is to provide a private key to the CLI to sign transactions it’s self. Please note, this is not the recommended way to interact with the CLI, but if you are just messing around on rinkeby, this will suffice.

To enable the feature, you first have to run the Aragon devchain.

aragon devchain

Once running you can stop it with Ctrl+c , a new hidden folder ~/.aragon will have been created. inside that folder create a new file called rinkeby_key.json inside that file copy the following changing the private key to one with some rinkeby eth preloaded.

  "rpc": "",
  "keys": ["put-your-priv-key-here"]

5. Testing

You can test it out by launching a rinkeby DAO right from the command line with:

dao new --environment aragon:rinkeby

if you are using frame add --use-frame to the end of the command

If all is well you should be able to open your new DAO at<your_dao_address>