All Aragon Devs Updates and Planning #47

Hi, I invite any team who would like to share their updates or submit discussion topics for the next Aragon Devs call to post them in this thread. The call will be held Monday April 27th .

Thanks :slight_smile:


Agenda and notes

All Aragon Devs #47 (Notes)

Call #46: April 27th, 2020 8am PST / 11am EST / 3pm UTC / 5pm CEST
Livestream / recording: https://youtu.be/L69B8IZKdCQ

Team Updates

  • See below

Agenda

Notes

Announcements

Aragon GitHub orgs: open invitation to anyone contributing to the Aragon projects to join the GitHub organization and get a badge + write access to some repositories.

Discussions

Dandelion

Emulates the Moloch mechanism to “ragequit” the org. (Demo of the token request feature.)

Agreements

(Demo of the specification document.)

The Agreements app is the glue between an Aragon Organization and Aragon Court.

Instead of creating votes for every action, the idea is to submit an intention of doing something to the organization, and having people challenging these intentions during a period of time. If no one challenges it, the action gets executed.

There are a lot of considerations involved with the constraint of having a period of time attached to every action, and how staking is attached to the intentions.

(Presentation of the different parameters and permissions needed in order to install the Agreement app.)

(Presentation of the path followed to execute an action.)

Demos

  • Inspired by aragonJS and toolkit
  • Work the same everywhere (nodejs, browser, etc)
  • experiment in aragon/plumbery
    • Core (base library)
    • Connectors (ethereum, thegraph)
    • Demos (organization viewer cli, organization viewer browser)
  • Research
    • Typescript (seems defacto standard for library)
    • Use Ethers.js (seems to be used by majority of project, newer the project more likely to user etheres)
    • Jest for testing
    • colonyJS a good source of inspiration
  • More info to be shared soon

App Installer

  • Gotten requests to install Redemptions and Token Request as standalone apps
  • Created a frontend to help people install one or both of them, provides an interface to select the DAO, checks its apps, asks for configuration options, and then creates a vote.
  • Supports most DAOs, but doesn’t currently support organizations with multiple token managers
  • User must have transaction path to create a vote, and vote has to be permission manager… but most organizations are configured this way.
  • Installs and sets permissions in one vote.

Attendance

1Hive: David, Fabri, Rodri

Aragon One: Brett, Facu, Luke, Pierre

1 Like

Aragon One

The past two weeks we have been primarily focused on:

  • Agreements architecture + integration into client
  • SDK/tooling redesign efforts
  • Building and integration automated Court notifications
  • Finalizing spring cleaning efforts

Topics

Next

Client

  • Agreements: contract implementation and integration

Court

  • Auto-reveal integration
  • Court email notifications backend + integration

SDK

  • New tooling efforts (code name plumbery)
1 Like

1Hive

Update

The last two weeks we have been primarily focused on:

  • Gardens
  • Apiary
  • Payroll
  • App installer

Discussions topics :

Relevant teams :

  • Gardens
    • Current:

      • Conviction Voting 1.0.0-beta.1 released on rinkeby (demo)
      • Gardens Template (demo). Things you can do:
        • Submit a proposal to conviction voting requesting Honey (Conviction Voting App)
        • Exchange Honey for organization tokens or vice versa (Fundraising App)
        • Support a funding proposal by staking organization tokens to it (Conviction Voting App)
        • Pay Honey to the organization to create a administrative vote (Dandelion Voting)
        • Burn organization tokens in exchange for a portion of Honey in the funding pool (Redemptions)
        • If you need Rinkeby Honey for testing you can mint it here
    • Next: Conviction Voting Milestone 4

  • Apiary
    • Current: Build profiles for Apiary (with A1)
      • May need to support them a bit to allow them to develop and contribute to Apiary
      • Possibly separate the workflows for different development (api, frontend). Make contribution easier
  • Payroll
    • Current:
      • Completed implementation and tests
      • Fiore working on designs
    • Next:
      • Bit behind on frontend implementation, bandwidth allocated to court dashboard, but will be available to push this forward in the next few weeks.
  • Radspec Registry
    • Next:
      • Use agreements instead of the contract we were thinking until now.
      • We are defering development for a few weeks until agreements is ready.
1 Like