Development

GitHub metrics

Developer activity (from Coinlib.io)

Developer activity (from Coinlib.io)

Ethereum addresses identify who you are interacting with. Who owns the organization, who creates a vote, where is the money being sent… Unfortunately, Ethereum addresses are long and hard to read. They don’t relate to the people we care about.

Today, that is changing. Aragon has introduced a powerful identity system. In the future, you will be able to plug in many different identity providers, like 3Box. But with Bella, they are starting with the simplest identity system. You see an address, you can click and tag it. The data never leaves your device, so you can rest assured that you are not de-anonymizing anyone. From that point on, you will not see that address anymore, but the name you assigned to it. It works all across the Aragon client. Then you can download a file with all your tags, and send it to other members of the organization.

A few years ago, could you ever imagine running a company from your phone?

Aragon released a mobile-compatible alpha version of Aragon at AraCon 2019. Since then, they have improved it so it’s ready for production use. You can check your organization’s activity directly from your phone. And not only that, but also interact with it. Vote, transfer tokens, see finances… all on the go.

Thanks to the new Aragon App Center, you can seamlessly upgrade apps in your organization. That means better functionality and bug fixes are just a click away.

Note that smart contract upgrades are always opt-in. Organizations decide how and when to upgrade.

With the new Activity panel on Aragon, you always know the state of the actions that you have initiated. Has the transaction been confirmed? How much time is remaining before it’s confirmed and settled?

With Aragon Payroll, paying your team members is easier than ever. You add a new employee and their details, and then they can request their salary in real time. They can also choose their salary allocation in different tokens offered by the organization.

This feature will be available to everyone soon.

There are also many minor fixes and improvements.

Discover the story behind Bella:

Luis and Jorge created their first company together at the young ages of 16 and 15. Discover how that experience shaped Aragon, and the Bella release.

Check out Twitter tread on Bella release.

Aragon Network Vote #2, the second vote held under the Aragon Governance Proposal (AGP) process, is scheduled to begin on April 25th, 2019 at 16:00 UTC.

Since the last Aragon Network Vote, a total of ten proposals were submitted for review before the deadline. The Aragon Association reviewed and then voted to approve nine of those proposals, which will now move on to the official ballot to be voted on by ANT holders.

What ANT holders are voting on

Here is the list of AGPs that ANT holders will be voting on:

AGP-9: The Separation of Church, State, and Network

AGP-28: Decentralizing aragonpm.eth

AGP-34: Flock Funding for Aragon Black

AGP-35: Edgeware Lockdrop Participation

AGP-37: Retainer for Ongoing Aragon Network Security Provider

AGP-40: Aragon Cooperative DAO funding proposal

AGP-41: Aragon Portfolio Diversification — Acquisition of DOTs

AGP-42: Keep Aragon Focused on Ethereum, not Polkadot

AGP-43: ANSP Engagement Policy

You can find a list of forum threads where each proposal is being discussed in the Aragon Network Vote #2 Megathread on the Aragon Forum.

How to vote in Aragon Network Vote #2

All ANT holders as of April 25, 2019 at 16:00 UTC will be eligible to vote “yes” or “no” on the AGPs above. The vote will last for 48 hours and then the results will be locked in via the Aragon Voting app.

The URL of the Voting app you will use for voting on all AGPs on this ballot is here.

Participating in the vote will not transfer any ANT from your wallet. The only funds that will be sent are the ETH used to pay gas for the vote transaction. Voting only requires interacting with the correct Voting app address; the ANT contract doesn’t need to be interacted with at all.

When the vote is proposed by the Aragon Association board at 16:00 UTC April 25th, a snapshot of ANT is automatically taken. ANT balances at that time will provide voting power for the vote.

If your ANT is stored by an exchange or an account that won’t be able to sign the vote transaction using one of the methods described below, please move your ANT before 16:00 UTC April 25th to an address that will be able to vote.

After the vote appears in the Voting app and the snapshot is taken, the ANT can be safely transferred back to your other account and you will still be able to vote with the address that had the tokens at the time the snapshot was taken.

Example of how you will be able to view how many tokens you can vote with using the Voting app

You can find more detailed instructions for the various ways you can vote with your ANT, along with documentation about how to cryptographically verify the proposals added to the ballot, in the Aragon Wiki. It is not necessary to cryptographically verify the proposals, but having this option available helps keep the vote honest and secure.

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

Publications on Aragon forum

Updates from Aragon chat (9th April -23rd April)

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

- Release Aragon 0.7

- AA review of AGPs

- Interacting with the Aragon community and being available for any AGP or 0.7 questions

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

- More ANV-02 prep

- More event planning

- Helped move AGPs through to the AA board review

- Worked on some logistics for upcoming events

- Worked some more on the new governance documentation

- Aragon 0.7 documentation

- Publish final details post for Aragon Network Vote #2

- Continue work on upcoming events logistics

- Planning for upcoming events

- Published the final details blog post for Aragon Network Vote #2

- Published Aragon 0.7 Bella user guide update

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

Aracon interview editing for the most part

- Continuing on the interviews to get the first round done

- Helping with Bella comms

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

- Prepared minutes and other legal docs

* HR Ops: contracts, amendments, equipment and vacations reviews

* Prepare send and sign legal docs

* Working on new hiring strategy

* Research feedback system

* Continue with pending HR legal

* Continue research on feedback system

* Define and implement first actions for the hiring strategy

- Coaching sessions with team members

- Offsite #6 misc

- Review all the new applications 🚀

- Execute payroll and reimbursements

- Coaching sessions with team members

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

- Agenda management

- Travel arrangements

- A1 HQ: supplies shopping, suppliers research & budgets review

- Misc. administrative tasks

- Accounting follow-ups

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

- Working on the App Center’s web3 data feed, connecting the frontend to it

- Reviewing @bpierre’s experiment on using React hooks in the Voting app (now merged 🎉)

- Reviewing @jon’s changes for signing messages (awesome contribution!)

- Publish aragonOS@4.2.0

- Deploy new set of contracts for `aragon-apps`

- 0.7 release related PRs, etc.

@bingen (Bingen Eguzkitza, Solidity Engineer):

- Trying to optimize Sortition with Checkpointing (Aragon Court issue #11, PR #28)

- Address Staking comments

- Review aragonOS PRs #505 and #506, aragon-apps #780

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

- Catch up to work done and future work

- Start work on pending tasks from Bella release

@gabi (Gabriel Garcia):

- Define aragonCLI testing roadmap #417

- Add sol-trace to aragonCLI

- New hack.aragon guide about Frame (possible Agent app)

@yalda (Yalda Mousavinia):

- Contribute to the forum, reviewing AGP drafts and more

- More testing, frontend fixes, sprint planning, logging of enhancement requests

- Begin home app design

- Begin profiles/identity design

- Rinkeby deployment script recommendations and fine-tuning

@danielnorman (Daniel Norman):

- Activity Panel

- Review signing messages

- Geth node monitoring

- Enable account button in menu bar

- 0.7 Release related PRs, reviews etc.

@danielconstantin (Daniel Constantin):

- finish ongoing work: aragen#32 , aragon.js#230

- review the PRs that piled up

- plan next few weeks & revisit the roadmap

@jon:

- continue working on the IPFS pinning backend https://github.com/openworklabs/pinning-service

- wrap up message signing in aragon/aragon https://github.com/aragon/aragon/pull/683

- set up hosting framework for server, db, and ipfs node

- I changed plans a bit in response to this awesome forum discussion https://forum.aragon.org/t/aragon-network-ipfs-pinning/824. Originally I was going to continue working on the IPFS Pinning backend, but it seems like we might change strategy, and I didn’t want to end up working on code that we wouldn’t use.

- Instead, I worked on the 3box < → Aragon integration, and most of the heavy lifting is done! https://github.com/AutarkLabs/planning-suite/tree/jon/identity/apps/identity . Now its mostly front-end / UI stuff. We also have some interesting stuff to figure out with regards to “what organizations a user belongs to” — a forum post coming on this topic soon.

- I also worked on summarizing a lot of our research about 3box, orbitDB and Textile, which will be published in a blog post. It’s being reviewed by these three teams.

- Continued working on the Aragon message signing.

@wade.alex.c (Alexander Wade):

-Worked with Diligence on what is now AGP-43

— The document proposes to give the AA some amount of discretionary authority to source security services outside of the ANV cycle

— Its goal was to provide some sense of direction to everyone regarding the ANSP relationship

-Reviewed changes for aragonOS@4.2.0, as several addressed findings from our baseline audit

— We recommended a few, minimal tweaks

— The branch was merged to master today!

-Wrapping up work on an advisory document to conclude our audit

— The majority of content is finished. The document proposes a three-part strategy to make changes to aragonOS, starting with simple, low-impact changes and leading into longer-term directions and goals for the project.

— I expect to have a draft of the advisory finished by tomorrow, and will be sending it to A1 / Diligence once complete.

@facuspagnuolo (Facu Spagnuolo)

- Payroll contracts last tweaks

- Help w/ apps and os releases

- Analyzing kill switch alternatives

- Draft different kill switch alternatives

See also: