Aragon core team developed Aragon apps (smart contracts + webapps)
bpierre Voting: updates (#448)
- Upgrade eslint.
- Move to parcel (from react-scripts).
- Move to react-spring (from react-motion).
- Card layout (issue: aragon/design#10).
- Display the user vote (“Your vote” badge) and the block number on the cards.
- Display the correct balance (PR: #449).
- Execute a vote (issue: #216 (comment), PR: #450).
- Explicitly change a vote (PR: #450).
- Fix the bars transitions.
- Update Aragon UI (fix the flickering when opening the sidebar on Chrome).
Latest commit d62f2b6 Sep 21, 2018

README.md

Aragon Apps Travis branch Coveralls branch

Apps

This repository contains the following apps:

  • Vault: Securely owns and manages tokens on behalf of a DAO.
  • Finance: Send payments and manage expenses with budgeting.
  • Voting: Create votes that execute actions on behalf of token holders.
  • Token Manager: Manages organization tokens.

You can read more about the individual apps in their specifications on the Aragon Wiki.

Coming soon apps

The following apps are still under development, not ready for production deployment yet:

  • Payroll: Manages employees' payrolls.

Developing

npm install

This installs global package dependencies and also bootstraps lerna packages.

Running tests on all apps can be done running npm run test at the root directory. Running tests of an individual app can be done by running npm run test inside the app directory.

By default tests are run in a in-memory instance of testrpc.

Issues

If you come across an issue with Aragon Core, do a search in the Issues tab of this repo and the Aragon Core Issues to make sure it hasn't been reported before. Follow these steps to help us prevent duplicate issues and unnecessary notifications going to the many people watching this repo:

  • If the issue you found has been reported and is still open, and the details match your issue, give a "thumbs up" to the relevant posts in the issue thread to signal that you have the same issue. No further action is required on your part.
  • If the issue you found has been reported and is still open, but the issue is missing some details, you can add a comment to the issue thread describing the additional details.
  • If the issue you found has been reported but has been closed, you can comment on the closed issue thread and ask to have the issue reopened because you are still experiencing the issue. Alternatively, you can open a new issue, reference the closed issue by number or link, and state that you are still experiencing the issue. Provide any additional details in your post so we can better understand the issue and how to fix it.