Development

GitHub metrics

Developer activity (from Coinlib.io)

Aragon Governance Proposals for the next Aragon Network vote are due in just under one month, on April 11th at 16:00 UTC.

To consolidate information about the upcoming Aragon Network Vote #2 John Light has created Aragon Network Vote #2 Megathread in the forum containing all important information about the vote.

In addition to using this thread for discussions, you can also use the Aragon Governance page 8 on the Wiki as the “single source of truth” for all important Aragon Governance Proposal (AGP) information and voting announcements. Any important updates will be linked there as soon as they’re announced through other official channels. So when in doubt, you can always check that page and have the most up-to-date info about the vote. The AGPs repo 5 will still be used for submitting AGPs and used as a historical archive of AGPs and Aragon Association review votes, but the wiki will be the main place to look if there are any questions about what the most up-to-date information is about an upcoming vote.

Dates for the next Aragon Network Vote

These dates may change if an emergency delay is approved by the Aragon Association Board of Directors. Check the Aragon Governance page 8 on the Wiki to confirm if you have any doubts.

Aragon Network Vote #2

Proposals for this vote are due, Aragon Association review begins: 2019–04–11 at 16:00 UTC

Aragon Association review ends, final community review begins: 2019–04–18 at 16:00 UTC

Aragon Network Vote #2 begins: 2019–04–25 at 16:00 UTC

Aragon Network Vote #2 ends, final results announced: 2019–04–27 at 16:00 UTC

Sign up for the voting alerts mailing list here.

For your reference

Here are some important links to be aware of pertaining to the AGP process:

Learn about the Aragon Governance Proposal process 3

Learn and discuss how to submit an Aragon Governance Proposal 2

Learn how the Aragon Association Board of Directors votes on proposals 2

Check out all open Aragon Governance Proposals 3

Vote on open proposals during an Aragon Network Vote 1

See results from past Aragon Network Votes

by Luis Cuende, CEO at Aragon One Team.

by Jorge Izquierdo, CTO at Aragon One:

The Aragon Court is a dispute resolution protocol that runs on Ethereum. It’s one of the core components of the Aragon Network.

The Aragon Court handles subjective disputes that cannot be solved by smart contracts. For this, it employs jurors that need to stake a token to the Court which allows them to get drafted to adjudicate disputes, that can earn them fees. The more tokens a juror has activated, the higher the chance to get drafted and earn more fees.

The Aragon Court attempts to find what the subjective truth is with a Schelling game. Jurors are asked to vote on the ruling that they think their fellow jurors are more likely to vote on. To incentivize consensus, jurors that don’t vote on the consensus ruling have some tokens slashed. Jurors that vote with the consensus ruling are rewarded with ruling fees and juror tokens from the jurors that voted for a minority ruling.

A design goal of the mechanism is to require very few jurors to adjudicate a dispute and produce a ruling. A small number of jurors is adjudicated by default to a dispute, and their ruling can be appealed in multiple rounds of appeals.

Even though the Aragon Court could theoretically resolve any type of binary dispute, in its first deployments it will be used to arbitrate Proposal Agreements. These agreements require entities creating a proposal in an organization to agree to its specific rules around proposal creation, putting some collateral at stake that could be lost if the Court finds the proposal invalid.

This first version of the Aragon Court has been heavily inspired by Kleros’ work. The code for the work-in-progress court has now been open sourced:.

This post is mostly a development update on the current state of the implementation and some aspects that team is still researching about and deciding on.

Updates from Aragon chat (12th March — 26th March)

@luis (Luis Cuende, CEO at Aragon One Team):

- Working on market segment analysis

- Improve and execute product management process

- Kickstart a new reporting process

- Kicking off Sprint 7 towards 0.7 launch!

- Ops stuff

- Think about how to make Ethereum great again

@light (John Light, Community at Aragon One):

- Catching up with comms after our offsite

- Finalize new comms docs

- Planning and logistics around upcoming events

- Preparing for the next Aragon Network Vote

- More Aragon Network Vote prep

- More upcoming events planning

- Review comms docs with the team, incorporate any feedback

- Publish blog post about AraCon with all photos and videos

@tatu (Tatu Kärki, Communications at Aragon One):

- Worked on a couple of team interviews

- Continued getting AraCon videos uploaded

- Some work on the wiki

- Get all AraCon presentation and panel videos uploaded and ready

- Working on blog posts

- Submit Aragon wiki page

@monica (Monica Zeng, Human Relations at Aragon One):

- Prepared an HR update

- Lead the team retrospective workshop

- Offsite #5

- Prepared and sent some contracts

- Worked on new calls system & new reporting process w Luis

- Review job applications

- Create, post and promote new job opening

- HR ops: compensation contracts

- Coaching + update team handbook with new guide

- Offsite postmortem + review Q2 goals

- Reviewed new application and interviewed some candidates

- Coaching sessions with 3 team members

- HR legal: prepared contracts minutes and preparing some new models

- Finish preparing new contracts and minutes

- March payroll and reimbursements

- Coaching sessions with 4 team members

- Review new applications and post new opening on the A1 new website

@LorenaGM (Lorena González, Assistant at Aragon One):

- Agenda Management & travel planning

- Administrative documentation review

- Execute payments

- Other administrative tasks (A1 Office HQ, taxes, misc. deliveries…)

@sohkai (Brett Sun, Lead Developer at Aragon One):

- Read, discuss, and triage baseline audit by authio (security partner)

- Get aragon apps frozen again for security review

- Provide data from aragon.js to the new App Center app

- Start modernizing Payroll’s contracts

- Aragon 0.7 contract changes + review baseline audit by authio

- Make changes in aragon.js to support upgrading apps in the App Center, turned out to be more complicated than initially anticipated

- Get Facu up to speed on Payroll

- Freeze aragonOS and aragon-apps again for security review

- Help finish the local identity changes

- Continue testing the changes for the App center

@bingen (Bingen Eguzkitza, Solidity Engineer):

- Review several aragonOS and aragon-apps PRs

- Review security report

- Review DevOps documentation

- Review Nest project milestones

- Review Aragon Court

@aquigorka (Gorka Ludlow, Frontend at Aragon One):

- Local identity integration too

- Export CSV data in Finance

- Wrapped up work on Local Identities / Custom Labels. PRs are hot and ready for review

- Submitted export data as csv in Finance PR

- Submitted toggle show/hide system apps in MenuPanel PR

- Wrap up Local Identities, Export Finance and Toogle show/hide system app PRs

- Modal component `aragon/ui` PR

- Let users know voting does not cost tokens update

- Transactions in activity panel

@yalda (Yalda Mousavinia):

- Determined that getting LinkedIn API access for useful fields like work history will not be possible due to LinkedIn’s stringent requirements on becoming a partner to access the data

- Finalized the job listing for FE developer role and began talking to potential candidates

- Conducted one user research interview (instead of three)

- Second wave of comments/questions on Aragon Black proposal

- Sprint planning: points estimation and analysis, assessing velocity, prioritizing tickets

- Finalized corporate structure / accounting tax classification. More banking research, but still unbanked

- Began drafting Autark monthly update and getting feedback

- Conduct one more user research interview + document highlights from last weeks + this weeks

- Try to lock down bank based on research from last week & various intros

- Complete any remaining design work for making our apps responsive

- Review more FE dev candidates / promote job listing

- Finish and publish Autark monthly update

- Collaborate with Arthur on forum post about monolithic apps/cross app UX

- Sprint planning: prioritizing tickets based on velocity analysis, add missing specifications as needed

@danielconstantin (Daniel Constantin):

- aragonCLI v5.6 milestone ( `aragon devchain — verbose` , prepackaging the gui client, `aragon ipfs propagate`, and a couple more issues)

- Review @aragon/api-react

- Revisit the “Simpler aragonAPI using events and promises” PR

@danielnorman (Daniel Norman):

- Local Identities integration across repositories

- Review/Update Infrastructure documentation

- Finish rxjs upgrade to v6 in apps

- Wrap up Local Identities PRs

- Caching to speed up initial load

@jon:

- Finished an initial discussions app backend spec

- Worked on discussion data formats

- Finish discussion spec

- Finalize v1 linked data formats for profiles and discussions

- Summarize our research, findings, and decisions

- Hopefully start coding on profiles!

@kevin.siegler (Kevin Siegler):

* implemented Cypress for E2E testing into the Planning Suite Monorepo

* Improved testing and test coverage on the Projects Contract

* Building frontend components for the Rewards App

* Created test app repo for FE dev job applicants

* Beginning to integrate Rewards frontend with the contract

@jackg (JackG):

- Coordinate with Diligence to wrap up the Baseline Audit

- Status update meeting with A1 devs

- Prepare Baseline Audit Report for publication on Monday before the All Devs Call

- Coordinate with A1 to implement the Recommendations from the Baseline Audit Report

@facuspagnuolo (Facu Spagnuolo)

- Onboarding tasks

- Keep working on the SVRP implementation

- Help Brett modernizing Payroll’s contracts

- Help reviewing contracts changes

See also:

All Aragon Devs #18 video.

Aragon App Development Survey — Autark would like to hear about your experience, especially if you had trouble or faced limitations. Please take a few minutes to take this brief survey and help us make it easier to #BUIDL with Aragon.