This guide will walk you through everything you need to add Token Request to an existing Aragon DAO.
Token Request has been published to the following locations:
token-request.aragonpm.ethtoken-request.aragonpm.ethTo deploy to an organization you can use the Aragon CLI.
The list of token addresses must be in ascending order, otherwise the installation will fail.
aragon dao install <dao-address> token-request.aragonpm.eth --app-init-args <tokens-app-address> <vault-app-address> ["'<tokenAddress1>', '<tokenAddress2>', ..."]
Token Request must have the MINT_ROLE permission on Tokens app.
This step is if you don't already have a DAO to install Token Request on, or want to test it on a demo first.
First, make sure that you have the Aragon CLI installed. Then run aragon devchain in a terminal. This should show you two Ethereum addresses. The first one has the most permissions and is used to execute commands on the Aragon CLI. Import the private key of that account into Metamask. Then head over to the Rinkeby DAO launcher and create a DAO with the democracy template. Make sure that the Metamask account that is active is the first account created by your aragon devchain.
Once your Democracy DAO is deployed (the voting params don't matter as you'll be the only one voting right now), go to the settings tab where you will find the addresses for the DAO and its apps. For legibility of subsequent commands will set bash environment variable for these addresses:
dao=0x6604f9fe9Db1D3F6a45d8F0ab79e8a4B05968816
tokens=0x7F42cEB659B944cBB9F3D5ED637f66818C1bAcbf
voting=0x41CA57d1e65Cdcd3A68A0e9f8E835F3a1FeDc655
vault=0x04b46b9e0c1f893cA50Cb35F096d14dD946DEf95