Development
Developer activity (from )
addresses identify who you are interacting with. Who owns the organization, who creates a vote, where is the money being sent… Unfortunately, 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 . 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 . 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 , 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 offered by the organization.
This feature will be available to everyone soon.
There are also many minor fixes and improvements.
Discover :
and 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 on Bella release.
:
Aragon Network Vote #2, the second vote held under the , is scheduled to begin on April 25th, 2019 at 16:00 UTC.
Since Aragon Network Vote, a total of ten proposals were submitted for review before the deadline. The Aragon Association reviewed and then 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:
You can find a list of forum threads where each proposal is being discussed in the 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
Participating in the vote will not transfer any ANT from your . 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 at the time the snapshot was taken.
You can find more detailed instructions for the , along with documentation about how to 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
Learn and discuss
Learn
Check out
Vote on
See results from
Publications on
Updates from (9th April -23rd April)
@luis (, 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 (, 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 for Aragon Network Vote #2
– Published Aragon 0.7 Bella update
@tatu (, 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 (, 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 (, Assistant at Aragon One):
– Agenda management
– Travel arrangements
– A1 HQ: supplies shopping, suppliers research & budgets review
– Misc. administrative tasks
– Accounting follow-ups
@sohkai (, 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 (, 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 (, 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
– Add sol-trace to aragonCLI
– New hack.aragon guide about Frame (possible Agent app)
@yalda ():
– 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: ,
– review the PRs that piled up
– plan next few weeks & revisit the roadmap
@jon:
– continue working on the IPFS pinning backend
– wrap up message signing in aragon/aragon
– set up hosting framework for server, db, and ipfs node
– I changed plans a bit in response to this awesome forum discussion . 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! . 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:
- video.
- Aragon Live Stream 18.04.2019 and .
- : 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.
Roadmap
Aragon Network
Current
Granular areas of focus with well defined scope and product specifications.
Allow people to delegate their voting power to delegates (i.e. representatives) who can vote on their behalf and continue experimenting with new voting mechanisms. Enhanced voting. Aragon One.
- Staking and Lock Managers
Provides a secure foundation for managing collateral deposits for agreements while allowing collateral assets to be used in to participate in governance. Dispute Resolution. Aragon One.
This deliverable includes the Aragon Court protocol, an interface for users of the court to review and manage agreements and disputes, and an interface for jurors to participate in the arbitration process. Dispute Resolution. Aragon One.
Near-term
Wider areas of focus with some flexibility on the scope.
Aragon Agreements are a core component of the Aragon Network, they enable users to define human-readable obligations and lock collateral to provide assurances to their counter-parties. Dispute Resolution. Aragon One.
Improve the experience and scalability of voting by implementing a protocol for votes to be submitted to a set of bonded relayers. Enhanced Voting. Aragon One.
Aragon Client
Current
Granular areas of focus with well defined scope and product specifications.
Make the platform and core apps responsive so Aragon can be used from mobile browsers such as Status or Cipher. Mobile experience. Aragon One.
- Local identity (custom labels)
As an intermediate solution for the full Aragon identity experience, we will allow people to create custom local labels to identify addresses that represent different members of the organization. Identity experience. Aragon One.
Finalize the development of the Planning Suite, which enables issue curation, allocating bounties as a DAO, budgeting via range voting, and on-chain mapping of human-readable names to addresses. Autark.
- Upgrading apps from the UI
Provide users with a secure way to upgrade app versions, fixes for features or enhancements to already installed/in use apps. App center. Aragon One.
This application will enable organizations to interact natively with other web3 applications (including other Aragon organizations). Agent application. Aragon One.
Allow organizations to distribute payments to holders based on the number of earned in a specific period (one-time reward) or based on total holdings (dividend). Autark.
This app will allow organizations to manage on-chain salary payments and for employees to request payments and see their available balance. UX improvements. Aragon One.
- Notifications & user feedback
Implement an activity panel that will provide people information about ongoing and past transactions as well as a toast component for immediate feedback on users’ actions. UX improvements. Aragon One.
Guided on-boarding of projects interested in collaboration with Aragon or use Aragon tools for their governance needs. UX improvements. Aragon One.
Allow organizations to manage their manifesto, mission statement, values, code of conduct, and contact information so it’s easily accessible to prospective and current members of the organization. Autark.
Near-term
Wider areas of focus with some flexibility on the scope.
- Browsing, installing & uninstalling apps
Enhance app discovery and app management for end users. Expand the on-boarding and app center experience. App center. Aragon One.
Allow individuals to create and manage their user profiles, mapping their address to a human readable name that can be used to interact with apps within the organization. Identity experience. Aragon One.
Allow individuals to associate additional details to their identity such as Github commit history, work history, portfolios, and membership to other Aragon organizations. Autark.
- Data Storage and Standards
Design the implementation strategy and information architecture for user profiles and contextual discussions. Document infrastructure solutions and recommendations for Aragon apps that require fast and queryable data that is hosted on distributed storage. Autark.
Research new organizational models, define the apps and permissions required to realize them and create kits that people can use. UX improvements. Aragon One.
- Organization identity & membership
Allow users to create and manage their organizations’ profiles, providing an intuitive way to add members to a given organization and granting them permissions & privileges. Identity experience. Aragon One.
Expand governance possibilities by providing more features for reputation-based organizations, including the ability to allocation non-transferable in place of (or in addition to) traditional bounties. Autark.
- aragonSDK: Split aragonUI and Lorikeet
Push Lorikeet as an ecosystem-wide project, while still providing an Aragon-opinionated experience with aragonUI. Lorikeet design system. Aragon One.
- Expanded Forwarder Options
Allow for more tightly coupled forwarder interactions where the forwarded call data can be leveraged and modified within the Forwarder contract. Autark.
Published at Tue, 23 Apr 2019 11:25:59 +0000
