Intro

We are so excited to announce the release of the new Aragon design system, a living project that will continue to evolve and further consolidate over the upcoming months.

This journey began a little more than four months ago, during a design sprint week, when we made the decision to "take a step back in order to move forward and faster". Building a design system from the ground up can be quite a challenge, but nothing is more rewarding than being able to witness its impact on the Aragon ecosystem, driven by an earnest passion, commitment, and team effort.

At this point the advantages of having a design system are very well documented. We can safely say that by adopting a systematic approach towards composing our UIs, we have completely changed the way we design and build products. From small startups to large organizations, single products to entire ecosystems, design systems help ensure products have a unified look and feel as they scale and mature.

If we had to reduce them to their essence, their core benefit: design systems allow teams to build better products, faster. This is what aragonDS is about.

What is a design system?

This systematic approach is nothing new. From the NASA manual published in 1975 to the award-winning GOV.UK’s and of course Material Design - the design tool with the greatest impact for the entire industry. Simply put, design systems are collections of components and patterns that can be combined, reused and extended to build products.

A design system ensures consistency and establishes a shared vocabulary. It reduces design debt, elevates quality while accelerating output, and builds a culture of inclusiveness and smoother collaboration between teams working together, to bring cohesive products to life.

Our approach & key objectives

We followed the Atomic Design methodology, which we have adapted to fit our design process, product offering, and team's context. Our approach to specifying the components and naming them is based on evolving a shared design language collaboratively and empowering all designers and engineers to contribute to the system.

Before we began our journey, we defined the objectives of our design system and outlined the guiding principles that we’ll follow throughout the process:

• To unify our brand and product design around a common, coherent, shared visual language.
• To ensure quality standards and consistency in how we use patterns and UI elements, as multiple teams need to work autonomously on various projects.
• To deliver products faster and more efficiently, reusing code and reducing custom instances to a minimum.
• To provide guidance and documentation to developers and designers wishing to build an Aragon app, so we support the scaling of the ecosystem.

We all agreed from the start that our approach had to be extremely flexible: after all, we already have a product and an ecosystem of apps relying on our UI toolkit. This is where these objectives became really useful: while aragonDS was taking shape, the new color system and the foundational elements were integrated in aragonUI, rebuilding one component after another, and used in apps as they became available. This list helped us to keep going in the right direction, while we were all busy shaping all these different pieces at the same time.

An additional challenge that we face when designing a system for a platform or app ecosystem is that, not only do we need to create components that fulfill our current requirements, but we also need to cater to future, unforeseen use cases, enabling app developers the expression of their own brand and purpose, while maintaining consistency and integrity.

aragonDS overview / sneak peak 👀

Principles

1. Consistent

Being consistent when designing an interface will give users a sense of predictability when browsing. We have drawn up a set of rules to ensure the construction of a sound, coherent, scalable base.

2. Hierarchical

The visual hierarchy is an essential element in any interface. The appearance of each item within the hierarchy is an indicator of its relative importance and its relationship with other elements, setting a well-defined order based on the user's visual axis.

3. Simple

Our interface is based on a straightforward, minimalist design with a lot of importance being given to the "white space" among the elements. This is to avoid 'cognitive overload' and thus make it easier for the user to explore and make decisions. The 'magic of design' includes making complex elements simpler.

4. Human

Design involves forging strong links with people, making things understandable and user-friendly, and giving help when it is needed. Resources such as illustrations, colors, and messages strengthen communication with the user.

Foundational elements

1. Color

We have created a color range that not only provides a more colorful interface but also guides users through a logical, coherent, consistent color scheme.

2. Grid

aragonDS bases its central content on a structure of 16 columns at maximum resolution and reduction to 4 columns at minimum resolution, with a separation between them of 16 px and a maximum resolution of 1104 px in keeping with the minimum unit size (8 px).

3. Font

We defined a main font within our choice of typefaces ("Overpass") and the secondary font ("Roboto Mono"). Both fonts are open source and are easily readable. They also have a great variety of typographic weights. The main font ("Overpass") will be used for all texts while the secondary font ("Roboto Mono") will be used for numbers given its high readability for this application.

4. Illustrations

We have worked on the creation and adaptation of the new style of illustrations to make it even more user-friendly. Illustrations that are dynamic and full of character help users to better understand the product. We also set great store by the use of color in each case, creating contrasts and adapting these to our interface.

Design guidelines

We are working on gathering all items, rules and principles within the Design Guidelines section of hack.aragon.org where you will be able browse each one of the sections in an easy, intuitive way.

The portal will be split into 3 sections, the first one giving an overview of the project, defining the pillars on which aragonDS is built. The second block will define and list each of the components and their properties, establishing a home page or index for easy browsing. And finally, there will be a summary of the present state of the web and future steps in the form of a timeline.

In this portal, you will be come up with new ideas, define components, and ask questions.

Testimonials

Here's what people that have started using our alpha release are saying about it:

“aragonUI makes your workflow much easier since you’re reusing a lot of the components in the library. The new design system makes it trivial to make your own custom components because you have clear guidelines and rules to follow.” — Deam Hansen, Front-end engineer at Aragon Black

“Building an Aragon app with the new design system and UI framework is amazing! The feature I love the most is how you can, with just a couple of components, build a grid where everything fits together so beautifully. Now building an Aragon app is so much straight forward enabling you to really focus on building your app rather than worrying on making it look good as that already comes straight out of the box.” — Fabrizio Vigevani, Software developer at 1Hive

“The new design system is very comprehensive and provides substantial guidelines for designing apps on Aragon with clean, intuitive components. At the product level, it's becoming a cornerstone for Flock cross-team collaboration and coordination on design decisions.” — Javier Alaves, Product Designer at Autark

But my favorite quote about the design system is from one of our Aragon One team members who, when using the Figma components library for the first time, said: “I feel like I'm playing with Legos! Using aragonDS feels like having a ton of shiny and ready-to-use LEGO bricks that we can play with to visualize our product ideas.”

Lorikeet

You may have heard of the Lorikeet project, which was started as an effort across multiple teams to build a generic design system for the decentralized web. The initiative was quite broad, and not specific enough to fulfill the needs of the Aragon platform, which aims for a strong sense of consistency and adaptability.

It also happened during a complicated time for decentralized projects, and most of the different participants had to shift their priorities during this year and realign their objectives, moving them away from Lorikeet.

This is why we decided to sunset Lorikeet as a project, and redirect our efforts to aragonDS and its toolkit, aragonUI. The efforts we put into it are not lost though: they helped us to learn more about our own specific needs, and paved the way towards aragonDS. It also served as a technical base for the new aragonUI.

aragonUI

aragonUI has been reworked at the same time, translating the principles defined by aragonDS into React components. It comes with a new theming system, multiple new components, and a refreshing visual update coming right from aragonDS.

We decided to name this version 1.0. The core Aragon apps have been ported to use it, and several others from teams like Autark, Aragon Black, 1Hive, and EmpowerTheDAO are on the way or already ported. It is still in preview, but even in the current state, it is fair to say that aragonUI is already more consistent, accessible, and easy to use than ever before.

During this redesign, we honed our work to be based on these guiding principles:

• aragonUI should be optimized for Aragon apps. It means that the API choices we make will favor what we believe should be expected by an Aragon app developer. Specific needs are also handled − we still plan to use aragonUI in different situations − but we want to provide the best experience possible to Aragon app developers.

• It should be possible to build a simple app without using any custom CSS. Some components are aware of what component they are in, and adapt their styles appropriately. The spacing is also managed by components when
  possible, but also lets users override it if needed.

• But anything outside of the simplest apps will need customized styling.
  That’s why components will let you extend them easily, by passing the
  className and style props to their main element. We particularly
  recommend using styled-components with its Babel plugin.

• Component APIs should have short and straightforward names, manifest the
  least surprising behavior, and offer the developer "one − and preferably
  only one − obvious way to do [something]" (from the infamous PEP 20)

If you develop Aragon apps, we strongly encourage you to try this early
version, and give us any feedback you have:

npm install -S @aragon/ui@next

You can find the upgrade instructions here.

As our immediate next steps, we will continue improving upon this foundation, adding more components to the kit and defining a contributor governance model for the design system. We’d also like to provide a chance for anyone using aragonDS to ask question and give feedback, so if you are interested in getting some one-to-one time with the team, feel free to reach out to us on the Aragon Forum or #design channel on Aragon Chat!

A glimpse into the future of organizations that you can use today

Tao or Dao is a Chinese word signifying the "way", "path", or "road", or sometimes more loosely "doctrine", "principle" or "holistic beliefs".

We use female Spanish names for Aragon releases, inspired by the story of Maria. Apart from there being a Chinese word called dao (DAO) that means the way, there is also a female Spanish name that means the way: Camino.

That’s why Aragon 0.8 is called Camino. We are paving the way to deliver Aragon to the users that need it the most. Let’s go over what makes Aragon 0.8 Camino special.

One app, endless possibilities

Announced earlier this year, Aragon Agent captured the imagination of people all across the Ethereum ecosystem. Protocols like Melon are already using Aragon Agent as a way to let an Aragon organization govern upgrades to their Ethereum contracts.

Aragon Agent enables organizations to interact directly with any Ethereum application. Whether you want your organization to own ENS names, lend its assets on Compound, or open a CDP on Maker, Agent makes it possible and visible for the whole organization.

Streamlined setup flow

The Aragon client now features more templates to match your needs. You can start a company, a membership, or a reputation-based organization in a few clicks.

Aragon is built to be modular, since the organizations of the future are not limited to just a handful of corporate structures.

Stay up to date with email notifications

New votes, financial transfers, changes in the permissions of the organization… you can now subscribe to all the events that matter to you. You won’t miss a vote anymore.

Raising the bar in design

From a new design system to re-designing the whole Aragon client, we put the utmost care in this new iteration of Aragon. We spent months listening to our users to create a brand new user experience that is more consistent, pleasant, and easier to use.

Simplified permission management

After user feedback, we decided to revamp the Permissions app. Permissions are such a core component of the Aragon vision and are extremely powerful once you understand them. But it was challenging to represent them in a friendly way, so we have built a new experience from the ground up.

Try Aragon 0.8 Camino today

Create your organization on mainnet today or create a test organization.

Do you want to help us on our fight for freedom? Check out job openings at Aragon Black, Aragon One, and Autark.

The aragonCLI is one of the most important tools Aragon users and developers have at their disposal. It is capable of interacting directly with the smart contracts that comprise an Aragon organization, making it more versatile and powerful than the graphical interface, at the cost of it having a steeper learning curve.

Due to the aragonCLI’s flexibility and advanced capabilities, it has remained a tool for Aragon power users and developers, and hasn’t received as much attention in our public-facing communications that are aimed at the average end user. With the recently announced Nest funding for our team, Aragon Mesh, who will be maintaining the aragonCLI for the foreseeable future, we plan to change that and start giving the aragonCLI more of the attention it deserves.

Going forward, you can expect to see major aragonCLI release announcements and feature deep dives published here on the blog, on the @AragonProject Twitter account, and on the #dev channel in Aragon Chat.

Announcing aragonCLI nightly builds and version 6.0.0

The first announcement we want to share should excite all aragonCLI power users. We are now releasing nightly builds of the aragonCLI so that users can access the latest and greatest features as soon as they are merged and ready for testing. For those who value stability we are keeping a list of battle-tested versions known as stable builds which you can easily switch between.

If you are interested in checking out the nightly build, run this command in your terminal:

npm i -g @aragon/cli@nightly

The second announcement is related to our last release (v6.0.0). We have decided to decouple the IPFS dependency because people usually have it installed already and because it is the type of dependency you want to install just once. Now the aragonCLI will check whether IPFS is installed in the project or globally and use that.

If you don’t have IPFS installed that’s alright too, as the new commands aragon ipfs install, aragon ipfs uninstall and aragon ipfs status facilitate the installation process. Learn more about them in the documentation.

Finally, if you run into any issues, jump on the #dev-help channel in the Aragon Chat and ask for help, or open an issue on the aragonCLI GitHub repo.

Until next time, happy hacking!

On July 27, 2019, Aragon Network Vote #3 concluded.

Eight Aragon Governance Proposals (AGPs) were approved by the Aragon Association Board of Directors to go on to the final ballot. Seven AGPs were ultimately approved and one was rejected by ANT holders in this vote.

Here are the final results from Aragon Network Vote #3.

Approved

AGP-59: Community Review Period

AGP-64: Support Quiet Ending Voting

AGP-67: 2019 Aragon Events Multisig Budget

AGP-70: Decentralize Nest

AGP-71: Nest 2019 Budget Extension

AGP-73: Flock Funding for Autark

AGP-75: The Aragon Governance Survey Process

Rejected

AGP-74: Single-purpose native mobile app for Aragon voting

Verifying the vote
You can double-check the results of this vote yourself in the governance.aragonproject.eth organization on Aragon. You can also see a data export of the vote results on Aragon One engineer Brett Sun’s public Tableau profile.

Feedback welcome

In the spirit of data-driven improvement, we invite all members of the Aragon community, voters and non-voters alike, to fill out a brief, six-question survey and give us feedback that will help us improve future Aragon Network votes. Anonymous results from the survey will be made public for the benefit of everyone interested.

Survey link: https://www.surveymonkey.com/r/2LHR9KR

Preparing for the next Aragon Network Vote

With this Aragon Network vote behind us, it’s now time to start preparing for the next vote.

Aragon Network Vote #4 is scheduled to start October 24, 2019 at 16:00 UTC. The deadline for turning in draft proposals for the new mandatory community review period is October 3, 2019 at 16:00 UTC, and the deadline for turning in final draft proposals for the Aragon Association review is October 10, 2019 at 16:00 UTC.

This gives Aragon community members a little over two months to prepare AGPs before the next vote. Check the Governance page in the Aragon Wiki for updates about Aragon Network vote scheduling and proposal deadlines in case there are any emergency changes. You can also subscribe to the low-volume Aragon Network Vote Alerts mailing list to receive important vote announcements straight to your inbox.

For complete details about how to make an Aragon Governance Proposal of your own, please review AGP-1, which defines the official process end to end. There are also links to additional resources about the AGP process on the Governance page in the Aragon Wiki. You can ask any questions you have about the Aragon governance process on the Aragon forum or Aragon Chat. And if you have an idea for an AGP that fits into one of the tracks defined in AGP-1, you are invited to start an Aragon forum thread in the Community category using the AGP tag so that Aragon community members can give you feedback about your proposal.

Congratulations and thanks

Congratulations to the authors of the proposals approved in this vote, and thank you to the AGP authors, reviewers, editors, contributors, and everyone who voted for participating in Aragon Network Vote #3 and helping to decide the future of the Aragon project! We look forward to seeing what the future holds for the next Aragon Network vote.

Aragon Network Vote #3 (ANV-3) is approaching, and with it a significant milestone for the Flock program.

In October 2018, the Aragon Association decided to radically decentralize the development of Aragon products by creating Aragon Flock. Aragon Flock is a grants program governed by ANT holders. It funds a set of core independent teams contributing to Aragon daily.

Last January, Autark’s first application to Flock got approved by the community, providing the team enough funding to run six months of operations. Two quarters forward, the Aragon Flock program is now three teams large, and the Autark team proposes to renew its membership for a year on the vote happening 2019-07-25, 16:00 UTC.

This is an important milestone for the Flock program as Autark would be the second team in Aragon’s history to be approved for a 12 months mandate after Aragon One.

All ANT holders are encouraged to review and vote on AGP-73!

Trying to make your life a bit easier, the Aragon Association compiled a list of links to go through before submitting your vote.

• Read through Autark’s June report
• Dive into the team’s official application… and the corresponding Forum discussion
• Check out a visual summary of what Autark is up to with its new application to Flock
• Finally, here is the In Flight Podcast episode featuring Autark’s team leader Yalda Mousavinia (@stellarmagnet) : “Conquering Mars with DAOs”

See you on Thursday to submit your votes on Autark’s proposal and the other seven proposals submitted by the community that you can find here.

Need better and easier ways to process information on Flock teams? The Aragon Association is open for feedback and demands from the community. Feel free to ping @louisgrx on the Aragon Chat.

The Aragon Association was born in December 2018, as a Switzerland-based Association, with Luis Cuende and Jorge Izquierdo as its board members.

In January 2019, Stefano Bernardi joined the Association to fulfill the Executive Director role. Since AGP-11 was approved during ANV-1, the Aragon Association has been focusing on executing its institutional mandate and corresponding deliverables.

In regard to the above the first months of the year have mostly been spent setting up the operational infrastructure for the Aragon Association, as well as facilitating coordination between Flock teams and, most importantly, prompt execution of the AGP votes.

In this report, we - the Aragon Association team - will share what we have accomplished so far and what we have planned for H2 2019.

Legal

• Set-up of the Association
• Contracts creation for Flock teams, Nest grants, service providers, etc.
• Contracts for employees and contractors

To-do:

• More work on fully decentralizing Aragon governance

Operations

• Hired first contractor: Louis Giraux
• Set up accounting infrastructure
• Execution of all AGP payments and contracts
• Participated in Edgeware Lockdrop per AGP-35; locked 20,000 ETH for 3 months and signaled with the full Association multisig ETH balance.

Treasury management

• Assessment of current treasury allocation and risk exposure
• Definition of a target balanced allocation for the treasury
• Set-up of infrastructure to be able to operate on markets
• Sold ~20,000 ETH for operational, Nest, Flock, and diversification needs at prices between 165 DAI and 265 DAI
• Per AGP-35, participated in Edgeware lockdrop (20,000 ETH locked and 156,136.562 ETH signalled)

To-do:

• Implementation of strategy to get to the desired portfolio allocation
• Explore options to provide easier ways for Aragon users to acquire ANT
• Continue working on transparency framework

Events

• AraCon 2019 coordination
• Sponsorship of community events

To-do:

• Planning and execution for a potential AraCon 2020

Nest

• New Nest grants allocated: Frame, Aragon Mesh, LevelK
• Nest mid-2019 community update
• Nest v2 proposal to be submitted to voters during ANV-3

Flock

• New security process (see) released and corresponding audits booked for Payroll and Fundraising app
• Tracking Flock team roadmaps and supporting delivery
• Collaboration to establish community report best practices with Autark

In progress:

• Booking audits for TPS and the Aragon Court system
• Implementation security DAO as per the new security process
• Taking over the organization and moderation of Aragon All Devs
• Update to the Flock proposal process (proposal guide)

To-do:

• Coordinate with Flock teams to establish Flock wide “OKRs"
• Establish on-boarding process and best work practices for Flock teams
• Organize all-teams-offsite besides AraCon 2020

Aragon communications

• Being available on forum.aragon.org
• Communication around ANV#2

To-do:

• Think about how AA communicates as a standalone entity.

Total 2019 Aragon Association budget spent

Expenses overview in CHF, through June 6th.

• Event sponsorship: 7,142.29
• Legal Fees: 37,191.67
• Salary cost: 98,971.27
• Other operating expenses: 36,521.54

Total 2019 Aragon Network Treasury spent

Expenses overview in CHF, through June 6th.

• Grants: 3,990,830.00

Aragon Network Vote #3 is scheduled to begin on July 25, 2019 at 16:00 UTC.

Read on for instructions about how to participate in the vote.

Since the last Aragon Network vote, a total of eleven proposals were submitted for review before the deadline. The Aragon Association Board of Directors reviewed and then voted to approve eight of those proposals, which will now move on to the 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 in Aragon Network Vote #3:

AGP-59: Community Review Period

AGP-64: Support Quiet Ending Voting

AGP-67: 2019 Aragon Events Multisig Budget

AGP-70: Decentralize Nest

AGP-71: Nest 2019 Budget Extension

AGP-73: Flock Funding for Autark

AGP-74: Single-purpose native mobile app for Aragon voting

AGP-75: The Aragon Governance Survey Process

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

How to vote in Aragon Network Vote #3

All ANT holders as of July 25, 2019 at 16:00 UTC (approximately) 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 Voting app when the vote ends on July 27, 2019 at 16:00 UTC.

Two different Voting apps will be used for voting on AGPs in this vote: one Voting app for Association, Finance, and Proclamation track proposals, and a different Voting app for Meta track proposals. The reason for using two Voting apps is because the Meta track requires a different support threshold for a proposal to be approved than the other tracks. You can read more about this in AGP-1.

The URL of the Voting app to use for Association, Finance, and Proclamation track proposals is:

https://mainnet.aragon.org/#/governance.aragonproject.eth/0x277bfcf7c2e162cb1ac3e9ae228a3132a75f83d4

And the URL of the Voting app to use for Meta track proposals is:

https://mainnet.aragon.org/#/governance.aragonproject.eth/0xcfee4d3078f74197ce77120dbfe6d35f443cab1c

Note that as one of the oldest Aragon organizations on the Ethereum mainnet, governance.aragonproject.eth may take 3-5 minutes to load depending on how fast the nodes you're connected to are. If you experience any issue viewing the open votes for Aragon Network Vote #3, please give the app time to load.

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 July 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 July 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.

You can find more detailed instructions for how to 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.

If you run into any trouble voting, check the troubleshooting section of the Aragon User Guide, and if the Aragon client continues to not work for any reason then you can vote using the raw transaction data below.

Raw vote transaction data

If you are voting from an offline wallet using MyCrypto or another tool for signing raw transactions, you will need the raw vote transaction data below. If you have any trouble using the Aragon client, you can also use the raw transaction data below to cast your vote using MyCrypto with any of the supported signing options.

AGP-59: Community Review Period

Raw transaction YES vote:

To address: 0xcfee4d3078f74197ce77120dbfe6d35f443cab1c
Value: 0 ETH
Data:
0xdf133bca000000000000000000000000000000000000000000000000000000000000000700000000000000000000000000000000000000000000000000000000000000010000000000000000000000000000000000000000000000000000000000000000
Gas limit: 120000

Raw transaction NO vote:

To address: 0xcfee4d3078f74197ce77120dbfe6d35f443cab1c
Value: 0 ETH
Data:
0xdf133bca000000000000000000000000000000000000000000000000000000000000000700000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
Gas limit: 120000

AGP-64: Support Quiet Ending Voting

Raw transaction YES vote:

To address: 0x277bfcf7c2e162cb1ac3e9ae228a3132a75f83d4
Value: 0 ETH
Data:
0xdf133bca000000000000000000000000000000000000000000000000000000000000001000000000000000000000000000000000000000000000000000000000000000010000000000000000000000000000000000000000000000000000000000000000
Gas limit: 120000

Raw transaction NO vote:

To address: 0x277bfcf7c2e162cb1ac3e9ae228a3132a75f83d4
Value: 0 ETH
Data:
0xdf133bca000000000000000000000000000000000000000000000000000000000000001000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
Gas limit: 120000

AGP-67: 2019 Aragon Events Multisig Budget

Raw transaction YES vote:

To address: 0x277bfcf7c2e162cb1ac3e9ae228a3132a75f83d4
Value: 0 ETH
Data:
0xdf133bca000000000000000000000000000000000000000000000000000000000000001100000000000000000000000000000000000000000000000000000000000000010000000000000000000000000000000000000000000000000000000000000000
Gas limit: 120000

Raw transaction NO vote:

To address: 0x277bfcf7c2e162cb1ac3e9ae228a3132a75f83d4
Value: 0 ETH
Data:
0xdf133bca000000000000000000000000000000000000000000000000000000000000001100000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
Gas limit: 120000

AGP-70: Decentralize Nest

Raw transaction YES vote:

To address: 0x277bfcf7c2e162cb1ac3e9ae228a3132a75f83d4
Value: 0 ETH
Data:
0xdf133bca000000000000000000000000000000000000000000000000000000000000001200000000000000000000000000000000000000000000000000000000000000010000000000000000000000000000000000000000000000000000000000000000
Gas limit: 120000

Raw transaction NO vote:

To address: 0x277bfcf7c2e162cb1ac3e9ae228a3132a75f83d4
Value: 0 ETH
Data:
0xdf133bca000000000000000000000000000000000000000000000000000000000000001200000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
Gas limit: 120000

AGP-71: Nest 2019 Budget Extension

Raw transaction YES vote:

To address: 0x277bfcf7c2e162cb1ac3e9ae228a3132a75f83d4
Value: 0 ETH
Data:
0xdf133bca000000000000000000000000000000000000000000000000000000000000001300000000000000000000000000000000000000000000000000000000000000010000000000000000000000000000000000000000000000000000000000000000
Gas limit: 120000

Raw transaction NO vote:

To address: 0x277bfcf7c2e162cb1ac3e9ae228a3132a75f83d4
Value: 0 ETH
Data:
0xdf133bca000000000000000000000000000000000000000000000000000000000000001300000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
Gas limit: 120000

AGP-73: Flock Funding for Autark

Raw transaction YES vote:

To address: 0x277bfcf7c2e162cb1ac3e9ae228a3132a75f83d4
Value: 0 ETH
Data:
0xdf133bca000000000000000000000000000000000000000000000000000000000000001400000000000000000000000000000000000000000000000000000000000000010000000000000000000000000000000000000000000000000000000000000000
Gas limit: 120000

Raw transaction NO vote:

To address: 0x277bfcf7c2e162cb1ac3e9ae228a3132a75f83d4
Value: 0 ETH
Data:
0xdf133bca000000000000000000000000000000000000000000000000000000000000001400000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
Gas limit: 120000

AGP-74: Single-purpose native mobile app for Aragon voting

Raw transaction YES vote:

To address: 0x277bfcf7c2e162cb1ac3e9ae228a3132a75f83d4
Value: 0 ETH
Data:
0xdf133bca000000000000000000000000000000000000000000000000000000000000001500000000000000000000000000000000000000000000000000000000000000010000000000000000000000000000000000000000000000000000000000000000
Gas limit: 120000

Raw transaction NO vote:

To address: 0x277bfcf7c2e162cb1ac3e9ae228a3132a75f83d4
Value: 0 ETH
Data:
0xdf133bca000000000000000000000000000000000000000000000000000000000000001500000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
Gas limit: 120000

AGP-75: The Aragon Governance Survey Process

Raw transaction YES vote:

To address: 0x277bfcf7c2e162cb1ac3e9ae228a3132a75f83d4
Value: 0 ETH
Data:
0xdf133bca000000000000000000000000000000000000000000000000000000000000001600000000000000000000000000000000000000000000000000000000000000010000000000000000000000000000000000000000000000000000000000000000
Gas limit: 120000

Raw transaction NO vote:

To address: 0x277bfcf7c2e162cb1ac3e9ae228a3132a75f83d4
Value: 0 ETH
Data:
0xdf133bca000000000000000000000000000000000000000000000000000000000000001600000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
Gas limit: 120000

What this data means (example)

It’s been a while since we have published an update about what has been happening inside the Nest program! In this post you’ll learn everything you need to know about the current and past Nest grantees.

The program initially launched in late 2017 in order to fund teams with innovative approaches to solving challenges in Aragon and the broader Ethereum ecosystem. In its first months, Nest received a number of awesome applications and quickly became an appealing grant program in the Ethereum ecosystem.

The majority of the teams presented in this update have been awarded a Nest Grant in 2018. The momentum acquired by Nest in its first months helped shape its identity. It also helped the program navigate the agitated waters of the bear market where it received its fair share of turbulence. Overall the learning curve has been steep, and the program’s team is always learning about how to make grantee’s experience as smooth and fruitful as possible.

At a time where we work hard to substitute human trust with technology, Nest is a bet on creating long lasting and trustful relationships working around Aragon’s mission. This is a precious aspect of the Nest program and we will do our best to foster this sense of community in the future.

With Aragon expanding, the Nest Program is refocusing on the Aragon ecosystem. 2019 grantees are working more closely than ever with the Flock program. Nest has also been proving itself as an opportunity to grow significantly and two former grantees were awarded a Flock membership in the past months.

Finally, we hope to turn Nest into an autonomous platform providing all the support they need to grantees. Doing a first step in this direction, the Aragon Association will propose Nest to be run as a DAO in Aragon Network Vote #3.

We are now pleased to relay updates coming straight from the Nest teams.

Any question about Nest? Ping @louisgrx on the Aragon Chat!

Nest team updates

Aragon Mesh

For those unfamiliar with the project, the aragonCLI is a tool used to develop Aragon apps, and to interact with DAOs (create, install apps, etc.). In April we've received a Nest grant to actively maintain the project and to plan for its development.

Our mission is to improve developer experience and to provide power users with an easier way of customizing DAOs without having to interact directly with the blockchain or to wait until the Graphical UI is fully-featured.

Initially this implied offering support to developers in setting up their environment, publishing apps, etc. This allowed us to prioritize bugs that prevent people from continuing their work and to add features that bring them the most value short-term.

What has changed
We have achieved a couple of milestones in regards to maintenance, which will free some of our bandwidth and which we hope that will enable a large number of contributors to get along:

• A monorepo structure
• Continuous integration
• Continuous deployment & a better changelog
• Unit & integration testing
• End-to-end testing
• Code coverage
• Automated dependency management
• Issue templates
• Code formatting
• Documentation on reviewing, testing, and releasing
• Updated API documentation & new guides
• Updated deployments of Aragon to the dev chain
• A nightly pipeline for users that value the latest updates & features
• A stable pipeline for users that value stability
• A single source of truth for API docs

Along the way we are also figuring out what are the best practices for developing:

• CLI tools
• JavaScript projects
• Community-driven projects

And, in a true web3 spirit, we've been documenting most of these in our repository.

Note: these are very early drafts that require a couple more iterations, but we are confident that soon, we will be onboarding new contributors in no time.

As far as new features go, the most noteworthy would be:

• aragon dao act
• aragon apm info
• aragon apm packages
• aragon ipfs propagate
• aragon ipfs view
• create-aragon-app

A lot of this work (if not most) has been done by the wider Aragon community and facilitated by us. A big thank you to everyone participating in this project!!!

And a special thanks to @sohkai who has been giving us a lot of valuable feedback along the way!!
👏👏👏

Challenges so far
One of the recurring issues people have with the CLI is that they cannot install it or that it stops working unexpectedly. This is often due to external dependencies and because "we" (the maintainers and Aragon community) don't install the CLI all the time, the first people to notice are new users. This is a terrible first experience, and people often think that it's their wrongdoing and become discouraged.

To tackle this, we wanted to set up end-to-end testing. We initially considered sharness because the IPFS folks are using it, but after some time decided to drop it due to shell scripting being difficult to learn and very time-consuming (as compared to node). As far as node frameworks go, we tried nixt and dropped it, favoring a few utilities we wrote that do the job well.

We also faced a few challenges when dealing with dependencies, lockfiles, monorepos or mocking dependencies in tests. If we can help you with any of these please reach out or check our internal docs! 👋

What is next
Being almost in a place where the aragonCLI is a stable and reliable tool, we will soon shift our efforts towards:

• The product spec, a place with current and future use cases
• A scalable architecture that allows people to extend it with ease
• Common building blocks to minimize code replication between extensions
• Curating good first issues
• Contributor incentivization
• Clearer priorities
• Better communication of releases & priorities

Until next time, happy hacking!

Aragon Mesh has been granted 100,000 DAI in April 2019 in order to operate for 6 months.

BrightID

About BrightID
BrightID is an identity network of unique humans. Its purpose is to keep fake users out of applications. It uses a decentralized, anonymous graph of people and records cryptographic connections made between them. We've created an algorithm to analyze the graph and make determinations about which vertices in the graph represent unique humans. The connection data is shared in a standard way, but server node operators can apply different graph analysis techniques for verification besides the one we provide as a reference.

It exists as a mobile application. We’re going through a beta test right now--if you’d like to contribute, please download the app, and join our Telegram or Matrix.

It’s an open source project on Github with wonderful volunteer contributors.

How did the project come into existence?
I created BrightID in late 2017 because there was no way to prove that someone is a unique human in a digital environment. In 2018, I was joined by several people I met at decstack and through Giveth’s social coding initiative.

BrightID was awarded a Nest Grant in Aug 2018 and launched in Jan 2019 followed by a demo at Aracon.

What’s next?
The most important update to BrightID this year will be launching app integrations. Here are our milestones for BrightID core for the next 5 months.

In the long run we are inspired by several areas where we think BrightID could be leveraged: for example Land Return, RadicalXChange, global Universal Basic Income, automated companies and services that pay dividends to all of humanity, social media that allows you to turn off fake accounts, groups and forums that allow effective bans, and worldwide votes. Eventually, people just won't put up with fake users, and they won't have to.

More information
BrightID whitepaper
BrightID website

Bright ID has been granted $90,000 USD equivalent in ETH in October 2018 for 4.5 months of work. The team received a 15,000 ANT reward for their work under Nest.

Prysmatic Labs

About Prysmatic Labs
Prysmatic Labs is a team working on core upgrades to the Ethereum protocol, including proof of stake and sharding. This initiative is part of the greater roadmap of Ethereum 2.0, an all-encompassing term for the next iteration of the Ethereum blockchain.

Prysmatic’s main project is Prysm, an open source client that implements the official Ethereum 2.0 research specification maintained here. In the same way as current operators of the Ethereum network run Geth or Parity nodes, we envision Prysm to be the de-facto standard of a production-grade node for Eth2.

What we’ve been up to lately

Milestones
We had three milestones upon receiving the first grant award. The first one was a proof of concept of an Ethereum 2.0 client, released in October 2018. The second milestone was a public test network for Ethereum 2.0’s phase 0, released Q2 2019 here. Our final milestone is set to release early 2020 as the public mainnet for Ethereum 2.0, in tandem with other clients. A stepping stone towards that final milestone will be a multi-client test network, set to release by end of this year.

We have achieved significant progress, growing the team to 6 individuals and have led by example in terms of creating a well-documented, tested, and strong client implementation.

Learnings
Eth2 has radically changed since we first started working on it and applied for the Nest grant. Originally, it was an extremely early, uncoordinated effort that very few teams were working on. There was little to no project management on behalf of the Ethereum foundation, and most of the research updates happened through scattered blog posts and markdown documents.

Since then, the initiative has matured significantly. There are over 8 teams working on Ethereum 2.0, and the Ethereum Research team has been fantastic and maintaining a solid specification through an official Github repository all teams contribute to. Throughout the process, we have learned how to deal with a moving target in terms of the underlying research of the protocol. We have always aimed to be on the bleeding edge in terms of our implementation, which has often led to big refactoring challenges as new bug fixes or better approaches are found in the specification.

What’s to come?!
Over the coming months, we aim to work closer towards interoperability for a multi-client testnet. That is, we are focusing on getting our codebase 100% aligned with the specification and working towards communicating with another client in the same way the current Ethereum network has many clients on it which implement the protocol. Our roadmap remains the same, and we expect to keep growing even more as a team and always learning from those around us.

_Prysmatic Labs has been granted $100,000 USD equivalent in ETH in June 2018 and is still working on delivering their ambitious roadmap.

Tennagraph

About Tennagraph
Tennagraph is the app for creation/collection of network sentiment for better Ethereum governance. Enabling more perspectives through:

• Coinvoting
• Gas Voting
• Rated influencer stances

https://tennagraph.com/

What We’ve Been Up To
Through the app we' gathered ~170 personal stances on EIP 1057 (ProgPow) from twitter. Added a new team member – Anett from Slovakia to help with community work. Also the community created several fundraising campaigns for us (now Aragon DAO, Giveth, GitCoin & WeTrust).

Last month we’ve Collected ~10 ETH donated for Tennagraph on gitcoin. It was used to produce a set of tweaks and improvements (like usability or interoperability with hive.one) identified after the launch.

Also we’ve made consultations with Hudson Jameson, Lane Rettig and more experts around the current state and further development. So far it proved to be interesting, with volume of votes to be a significant improvement in the future.

What’s Next
Now we’re researching further directions for development (integration with github, eth address clusterization and more)info is coming soon. Thanks again to all supporters, including the Aragon, Gitcoin, Hudson Jameson and many more. You can follow more updates on Tenna’s twitter account.

Tennagraph has been granted 15,000 DAI and a 6K ANT reward for their work under Nest in 2018.

Level K

About Level K
This is Level K ’s first update, but there is much to talk about. Level K was started in 2017 and develops decentralized applications. We were given a Nest grant in December 2018 to build an Aragon futarchy app, and deployed our first version of this app to Rinkeby in March.

More recently Level K was awarded a Nest grant to build an Aragon Oracle Manager app and to utilize it along with the Aragon futarchy app to launch futarchy signaling markets for the Aragon Network Vote. We are currently working on the oracle manager app and providing an integration with Uniswap as a price feed oracle.

What We’ve Been Up To
Futarchy has been theorized to be a powerful tool for governance for determining how to best achieve some already defined objectives. Organizations would continue with current methods of setting values and objectives, but futarchy could help make decisions around how best to pursue the organization’s values/objectives.

Back in April, 2018, Level K proposed a couple approaches on how to implement futarchy. We built on our previous work with Gnosis around implementing the first option described where there is a categorical market for the outcomes, and scalar “conditional” markets for each outcome predicting the impact on the success metric under the condition of the given outcome.

The code for the futarchy app can be found at https://github.com/levelkdev/futarchy-app. We first deployed the Aragon futarchy app to Rinkeby in March and are currently looking for beta testers. If interested please reach out to contact@levelk.io.

The current version of the futarchy app is designed to use an ERC20 token price point as the metric of success, and relies on a centralized oracle to report this price point. In order to be a reliable mechanism for decentralized governance, the futarchy app should rely on a decentralized price feed. The motivation for building the Oracle Manager App is to provide this decentralized price feed to the futarchy app, or to any Ethereum dapp that chooses to utilize it.

Level K has also been considering how best to test futarchy and bring it live. Through our discussions with the Aragon One team, we hatched the idea to launch “signaling markets” for specific proposals in an Aragon Network Vote. The idea is to run futarchy markets for an AGP decision alongside the actual voting during an Aragon Network Vote. The markets will allow anyone to bet on the impact that a given AGP decision will have on the price of ANT. The futarchy markets will not trigger the actual decision. We can observe how people interact with futarchy, and how the outcome of the futarchy markets compare with the actual decision. And if the futarchy market decision is the same as the actual decision, we can see how the predictions on the ANT price play out over time. Deploying a signaling market for an AGP decision is part of the work for the current Nest grant.

What’s Next
In the coming months we aim to deploy the Aragon Oracle Manager App to Rinkeby with an interface to Uniswap. We also plan to run beta tests for the Aragon Futarchy App (if interested in participating reach out to contact@levelk.io) and to develop an Aragon DAO kit for easy setup of an Aragon DAO that uses futarchy. This work will culminate in the launching of futarchy signaling markets alongside an AGP vote on main net. Level K will soon release a more detailed road map about our plans with futarchy. For more information about how futarchy might be used by Aragon, check out this post on Futarchy Courts. We’re excited for the promise futarchy holds for on chain governance.

Level K has been granted 130,000 DAI for their second Nest grant in May 2019. They received a 25,000 ANT reward for their work on Futarchy completed under their first Nest grant, which was for 80,000 DAI.

Espresso

We are pleased to announce the first demo release of the Espresso Drive! This release also marks the end of our Aragon Nest program and before we begin with our recap, we would like to thank Aragon for giving us this incredible opportunity and for providing all the help and support that we needed during our development. It was truly an amazing experience to be part of the Nest program.

If you are not familiar with the app, Espresso Drive is an Aragon application that aims to provide a Dropbox-like user experience for decentralized storage. It is specifically built for DAOs and currently supports IPFS and Swarm. Here is the link for the demo.

What’s New?

Folders and labels
Up until now, it was only possible to share files individually, so sharing 10 files would require 10 separate actions. This is far from an efficient process, quite costly and repetitive. It is now possible to create folders to group these files together, making the sharing process much easier and enabling more diversified classification structures.

When a folder is shared with another user or group, every file and subfolder inside it will automatically inherit the appropriate permissions, with a single transaction. Labels are now also available.

Comment threads, file recovery, and search bar
Efficient communication is crucial to an organization’s success, and DAOs should be equipped with tools that facilitate the exchange of information. This is why we are introducing a new comment section where users have the possibility to add notes, leave feedback and express their thoughts. Each file has its own comment thread. A new search bar and a file recovery feature are also now available.

Other Improvements

• Loading icon
• Input validation
• Identity Badges
• Improved documentation
• Frontend moved to the Drive repository

What’s Next?

Being able to store files privately is probably one of the most important feature that remains to be integrated into the Espresso Drive. In the previous months, we began implementing basic encryption algorithms and the app now supports AES with the CBC and GCM modes, both available with 128-bit and 256-bit keys. The next step will be to handle the management of the encryption keys.

Another task we are planning to do next is to refactor the Groups section and create a standalone Aragon app from it. We believe the app would be valuable to many developers as groups are a fairly common pattern found in numerous apps. Mathew, one of our members, has also started working on a new Solidity tool called Quantal.

Espresso has been granted $100,000 USD equivalent in ETH in July 2018 and a 15,000 ANT reward for their work.

Dappnode

Let us start with a quick refresher of the DAppNode project: DAppNode aims to truly decentralize the infrastructure layer of P2P networks like blockchains or DApps. And it does that by providing Open Source software that makes it as easy as one-click install to start running nodes for these networks. In this way, we can eliminate the reliance on centralized 3rd parties to run decentralized systems and we open the door to incentive schemes for users to be paid to run nodes and strengthen the network. For more information you can check this post!

We would like to thank the Aragon Nest project again for its support! DAppNode is a firm believer in Aragon. Our package registry uses the Aragon Package Manager and is a permissionless system for devs to register their packages install it in any DAppNode. Not only this, but we were also the first DAO in the Ethereum mainnet!

https://twitter.com/izqui9/status/974203914659729408

Let’s jump right in on the updates since the last time, which you can find here.

Tools, tech and core packages

• Our SDK has been updated to help devs develop and publish their DAppNode packages on DAppNode, available then with an IPFS hash or with an ENS domain. This was a great step that gave more functionality and value to DApp developers. We have now provided them with a graphic interface to assist in the final steps of publishing a package, right from their DAppNode’s UI.

• In v0.2.0 we changed our base OS to Debian since they have a fully Open Source policy and it’s maintained by the community. We also changed to OpenVPN as the method to connect to the DAppNode from anywhere since it’s more stable and also completely Open Source.

• The IPFS package and its web UI has been updated, and the overall performance of IPFS as core package of DAppNode has been greatly improved, sometimes you do not even notice you are using IPFS. We have also added a feature that allows to p2p connect two IPFS nodes with one click.

Usability

• A major redesign of the ADMIN UI has been completed, making it more useful and user-friendly: we implemented a notifications tab that informs the user about important issues regarding the status of DAppNode and we included an auto-diagnose tool in the ADMIN UI. In addition, users can now also see complete info of all the installed packages and directly report issues from the admin UI with a pre-populated template that gathers relevant info from the DAppNode (always optional).

• In case the Nodler (the DAppNode user) has a dynamic IP (like the majority of us), we have implemented a DynDNS server that allows the IP of the DAppnode to always resolve to a fixed domain XXXXXXXXX.dyndns.dappnode.io so Nodlers do not need to pay any internet provider for a static IP, but still can have their DAppNode visible when their IP is changed by any ISP. In addition, users that have a static IP can now set it up in the DAppNode.

• Nodlers can now select in the installation the ports to be used by the installed package and also the path in which packages/volumes will be installed. The option to upload and download files to and from any package is also available and it is possible to set up environment variables to customize the operation of each package, either in the installation or after it.

• Nodlers are now able to see logs of the DAppNode in the AdminUI. We believe it is important to give users access to these logs without being obliged to perform any task on the console, this also helps us to provide better support as these logs can be easily downloaded in a JSON file to be analyzed by our team.

• Servers where DAppNode is installed are now protected from being overfilled with chain data until the point it makes the server useless: there are now two security thresholds that stop packages from downloading more data when the disk is near full capacity, and Nodlers get a notification so they can act on it.

• We have included a WIFI package that allows a seamless connection to your DAppNode without the need of connecting via VPN.

Content

• Ethereum, Bitcoin and Monero nodes are now available in DAppNode. For testnets we support Rinkeby, Ropsten, Kovan and Goerli

• In terms of DApps you can now install with one click Swarm and Status and we’ve just added Vipnode and Artis. Non that long ago we announced our partnership with Raiden and we will have it available in DappNode very soon! And, shhh! We have some ETH2.0 validators running for testing prior to an official release in our installer.

Others

• We have developed an NFT issuer as an Aragon App.

• Since not everyone has a spare machine to dedicate to running DAppNode, we have started selling pre-installed DAppNode Boxes that work plug and play!

What’s next?
We have a lot in store in our roadmap, but I think it can all be summarized by: content, content and content! We are working very hard to bring nodes to strengthen the networks we love. In this initial phase we have made it very simple for everyone to run a node, so our next phase is going to be all about bringing in content to the DAppNode, to increase its utility value and create more network effects.

Dappnode has been granted $60,000 USD equivalent in ETH in July 2018 and has received 25,000 ANT as a reward for their work under Nest.

Pando/Apiary (WIP)

A leap forward for decentralization and sustainability!

Much progress has been made in the development of Pando, a politically and architecturally decentralized alternative to Git leveraging the governance capabilities of Aragon OS, and that of Apiary, that has become the Fundraising app for Aragon DAOs.

By a vote of ANT token holders during Aragon’s 2nd Network Vote, we’ve been humbled and honored to join Aragon as the 3rd Flock team: Aragon Black.

Aragon Black Flock proposal

As a Nest grantee that has made the leap to fully fledged Aragon team we aspire to set an example for other grantees and the larger ecosystem.

This is a crucial matter in the fight for freedom and decentralization: inspiring and enabling committed and passionate contributors from around the world to participate in the development and adoption of a protocol enabling the emergence of unstoppable and modular organizations.

We will soon be presenting a more complete report on the progress of the Aragon Black Flock, however we can already share some developments on the Nest front.

Fundraising

Steadfast progress is being made on the Fundraising app and we are nearing launch.

We have sent to audit the following smart contracts used by the Fundraising App: Fundraising Controller, Batched Bonding Curve, Collateral Pool, Tap. Results are expected to be delivered this month.

The front end development is in the final stage with a view of publishing a Rinkeby app after audit results are delivered and relevant adjustments are made.

The team is finalizing the Fundraising Template (ex-kits) for deployment by DAOs via the CLI (and later on from the Client’s UI)

These efforts on the app are followed in parallel by research on a Fundraising library that will allow the configuration of various curve types, initialization parameters and taxation mechanisms. As the app launch is getting closer, we are finalizing the specification for the v1 library.

On the community facing side of things we’ve released a blog post presenting Fundraising at a high level. The blog post was widely shared in the community and received numerous applications for on-boarding. This effort is being followed through with governance and curve design workshops.

Pando

In May we released the Rinkeby version of Pando Network that can be accessed here!

This version allows for pushing commits via the command line interface as well as repository creation and approving pull requests both via CLI and the Aragon client UI.

With aragonOS’s permissions system you can for example set up a repo to allow the core developers to directly commit while allowing any other contributor to submit a pull request that is approved by the Voting app.

You can also now connect your DAO-controlled Pando repo to git/GitHub and your favorite extensions thanks to a git-remote protocol.

More recently there have been intense under the hood work as we refactored the library after a major IPFS update where IPLD.js moved from using callback patterns in their API to using promises.

With that we took the opportunity to create types for the different data structures to make it easier for our front-end to consume and send data to IPFS.

Pando is nearing its first user facing update by enabling markdown editing of repository content directly from the UI. This update requires an upcoming update of aragonCLI to support the above IPFS library updates and will be published later in the summer.

What’s next
Shipping to the public the Fundraising App is our priority!

Through the on-boarding process we have identified commonly demanded curve types and will be focusing on delivering a constantly evolving library of bonding curves.

Research on IPFS pinning and merging is ongoing while we continue developing and enhancing the features of Pando in view of a mainnet launch, as well as developing a GitHub2Pando script to synchronize GitHub and Pando repositories on a regular basis.

The Pando team had received a grant of $100,000 USD equivalent in ETH to work on Apiary in December 2018 and gave up on part of this grant when they transitioned into a Flock team. They had also been granted $107,000 USD equivalent in ETH to work on the Pando Network app in March 2018. Finally, they received a 25,000 ANT reward for their work on the Pando Network app.

Frame

At Frame we’ve been hard at work on meaningful account and infrastructure updates.

Smart Accounts
Smart accounts will change the way we use the web. In v0.2 we’ve added support for an important type of smart account, Aragon DAOs. Enabled by Aragon Agent, you can now add your DAO as an account in Frame and use it to interact with any dapp on behalf of your DAO. This opens the door to endless possibilities using your DAOs to interact with the decentralized web.

More Account Updates
In v0.2 accounts are now persistent. This means you can use your accounts even when your signer is asleep or disconnected. You’ll only need your signer to be available when signing a payload.

In addition to smart accounts we've also added hot accounts. Hot accounts store your private keys on your machine rather than using a hardware signer. They can be created with a mnemonic phrase, private key or keystore.json file.

Unstoppable
We believe Frame should be truly decentralized and unstoppable. Any user, regardless of technical understanding, should be able to pilot Frame without relying on centralized services. To support this effort we’ve been expanding the underlying infrastructure of Frame. In v0.2 users will be able to run Ethereum light clients and IPFS gateways with the flip of a switch.

Future & Flock
We’re excited to be working on the Aragon platform. We're focused on extending the abilities of Aragon DAOs via provider and signer level integrations. Our goal is to make using and interacting with Aragon DAOs as seamless and intuitive as possible. As part of our commitment to Aragon we will be submitting a Flock proposal. We hope the Aragon Network will support us working on this effort full time.

Frame has been granted its second Nest grant in April 2019, amounting to 120,000 DAI. They have received a 25,000 ANT reward for their previous work under Nest.

Autark

About
Autark began contributing to the Aragon ecosystem in April 2018 when we were funded by the Nest program to build That Planning Suite, a suite of Aragon apps that allows organizations to curate issues, collectively budget, and design custom reward & bounty programs.

What we have been up to lately
On January 26, 2019, we were officially voted in to become a full-time Flock team when AGP-19 passed. We subsequently launched That Planning Suite to Rinkeby in April 2019, and received organic interest from p2pmodels, 1hive, and Aragon Mesh. Autark is now rebranding That Planning Suite to Open Enterprise.

Lately we have been building out many of the features defined in AGP-19 such as profiles, discussions, a customizable home app, and general upgrades to Open Enterprise. As far as this Flock work goes, we have written detailed updates in our transparency reports which are located at blog.autark.xyz.

What’s next
Security audits for Open Enterprise have just began and we are aiming for a Mainnet release no later than Q4 2019.

We are applying for our second Flock grant in Aragon Network Vote #3 which begins July 25, 2019. Check out our proposal and provide feedback.

As we have concluded our Nest work, please follow our future updates on our Flock work at blog.autark.xyz!

The Autark team working on The Planning Suite (now renamed to Open Enterprise) has been granted a grant of $150,000 USD equivalent in ETH in April 2018 and gave up on part of it when they became a Flock team. The team received a 25,000 ANT reward for their work under Nest.

Thanks to John Light and Nest team members for their contributions to this post.

Learn more about Nest on GitHub

With the release of Aragon 0.7 Bella, organizations now have the ability to upgrade their apps to the most recent versions from the organization’s App Center. This is the first time (that we’re aware of) that end-users of a decentralized app have been given the ability to upgrade their app - including the smart contracts - independent of the developer.

With Aragon Network Vote #3 just a few weeks away, we want to give voters the best experience possible, which includes adopting all of the improvements that have been made to the apps used by the Aragon Governance organization. To this end we are scheduling a vote to upgrade the apps of the governance.aragonproject.eth organization to their latest versions. All ANT holders are invited to participate in this historic first vote to upgrade the apps of the Aragon Governance organization.

The vote to upgrade the apps of the Aragon governance organization is scheduled to begin on July 15, 2019 at 16:00 UTC.

The vote will use the same Voting app as used for Meta track Aragon Governance Proposals, so voting will be open for 48 hours, requiring >66.66..6% support and >0% minimum acceptance quorum for proposals to be approved. This means as long as more than approximately two-thirds of tokens that participate vote “yes” on the proposals, they will be approved.

The apps that will be upgraded are: Vault, Voting, and Finance.

Voting “yes” will support adopting the upgrades to the latest version of these apps as of the time the vote has started. Voting “no” will support staying on the current versions of the apps.

The changes that will be adopted with each upgrade include bug fixes, feature enhancements, and user experience improvements, including faster app loading thanks to better caching, all of which adds up to a better experience for ANT holders when they are using the apps in the Aragon Governance organization.

How to vote on upgrading the Aragon governance apps

The voting process is the same as it is for voting on Aragon Governance Proposals, so if you have experience and know how to vote, then you can skip straight to the Voting app URL below to participate in the vote at the designated time. Instructions for voting with raw transactions are also included at the end of this post.

All ANT holders as of July 15, 2019 at 16:00 UTC (approximately) will be eligible to vote “yes” or “no” on upgrading the apps of the Aragon governance organization. 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 the app upgrades is:

https://mainnet.aragon.org/#/governance.aragonproject.eth/0xcfee4d3078f74197ce77120dbfe6d35f443cab1c

Note that as one of the oldest Aragon organizations on the Ethereum mainnet, governance.aragonproject.eth may take 10-20 minutes to load depending on how fast the nodes you're connected to are. If you experience any issues viewing the upgrade votes, please give the app time to load. This loading time will be improved during future votes if the proposal to upgrade the Voting app is approved!

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 July 15th, 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 July 15th 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.

You can find more detailed instructions for how to vote with your ANT in the Aragon Wiki. If you run into any trouble voting, check the troubleshooting section of the Aragon Knowledge Base, and if the Aragon client continues to not work for any reason then try voting with the raw transaction data below.

Raw vote transaction data
If you are voting from an offline wallet using MyCrypto or another tool for signing raw transactions, you will need the raw vote transaction data below. If you have any trouble connecting to the default node used by the Aragon client, you can also use the raw transaction data below to cast your vote using MyCrypto with any of the supported signing options.

Kernel: Upgrade 'vault.aragonpm.eth' app instances

Raw transaction YES vote:

To address: 0xcfee4d3078f74197ce77120dbfe6d35f443cab1c
Value: 0 ETH
Data:
0xdf133bca000000000000000000000000000000000000000000000000000000000000000400000000000000000000000000000000000000000000000000000000000000010000000000000000000000000000000000000000000000000000000000000000
Gas limit: 120000

Raw transaction NO vote:

To address: 0xcfee4d3078f74197ce77120dbfe6d35f443cab1c
Value: 0 ETH
Data: 
0xdf133bca000000000000000000000000000000000000000000000000000000000000000400000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
Gas limit: 120000

Kernel: Upgrade 'voting.aragonpm.eth' app instances

Raw transaction YES vote:

To address: 0xcfee4d3078f74197ce77120dbfe6d35f443cab1c
Value: 0 ETH
Data:
0xdf133bca000000000000000000000000000000000000000000000000000000000000000500000000000000000000000000000000000000000000000000000000000000010000000000000000000000000000000000000000000000000000000000000000
Gas limit: 120000

Raw transaction NO vote:

To address: 0xcfee4d3078f74197ce77120dbfe6d35f443cab1c
Value: 0 ETH
Data: 
0xdf133bca000000000000000000000000000000000000000000000000000000000000000500000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
Gas limit: 120000

Kernel: Upgrade 'finance.aragonpm.eth' app instances

Raw transaction YES vote:

To address: 0xcfee4d3078f74197ce77120dbfe6d35f443cab1c
Value: 0 ETH
Data:
0xdf133bca000000000000000000000000000000000000000000000000000000000000000600000000000000000000000000000000000000000000000000000000000000010000000000000000000000000000000000000000000000000000000000000000
Gas limit: 120000

Raw transaction NO vote:

To address: 0xcfee4d3078f74197ce77120dbfe6d35f443cab1c
Value: 0 ETH
Data: 
0xdf133bca000000000000000000000000000000000000000000000000000000000000000600000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
Gas limit: 120000

Aragon Fundraising, previously called Apiary, is an app built on top of Aragon, providing Aragon users an easy way to raise funds through an emergent organization. It has been developed by the Aragon Black team and will be available on the Ethereum mainnet by the end of 2019.

This innovative model distinguishes itself by leveraging aragonOS’s apps ecosystem and permissions system, a batched bonding curve implementation that incentivizes “skin in the game” and curation with multiple collateral token support, novel measures preventing front-running, and a tap mechanism that sustains the underlying project while safeguarding the majority of funds from depletion.

Splitting funds into reserve and discretionary pools provides smart contract-enforced accountability between project contributors and patrons throughout the lifecycle of a project while simultaneously ensuring sufficient liquidity to support the emergence of a long-tail of organizations.

Architecture
The Aragon Fundraising app architecture is based upon Vitalik Buterin’s description of a Decentralized Autonomous Initial Coin Offering (aka DAICO) and Luke Duncan’s seminal research about emergent organizations.

The cornerstone of this application is a bonding curve smart contract: an automated-market maker where any user can deposit collateral in exchange for an organization-specific token. This market maker accepts both ETH and / or any ERC20 as a collateral. However, our first released default template will be set to accept DAI and ANT only (for a curve behavior that’s as intuitively readable as possible) although customization will be available at a granular level through the use of the aragonCLI.

The market maker contract mints tokens to stakers at a price determined by the initialization parameters according to the existing token supply. This guarantees continuous liquidity while incentivizing curation and funding for social good.

The collaterals deposited along the curve are automatically transferred into a reserve pool. However, the funds held in this reserve pool cannot be spent directly. A tap mechanism controls the percent of this reserve that can be withdrawn in a given time period to a discretionary vault to encourage a reasonable use of the funds. Token holders of the organization can then vote to allocate funds held by the discretionary vault and fund the tasks their project encompasses.

Sensitive actions such as raising the tap are permissioned so that changes require consent of the patrons. There is even a patrons-controlled 30 day buffer for raising tap percentages in case a conflict arises. Setting a continuously updatable tap for raised funds instead of a lump sum transfer provides accountability and alignment of interests between different parties related to the curve (founders, contributors, stakers, wider community, etc.). The Fundraising app thus enables exploration, curation, and staking into networks that are allocating and producing value as Decentralized Autonomous Organizations (DAOs).

Modularity
The Aragon Fundraising app has been designed to be as modular as possible. Market-making, token management, withdrawal of funds and control of these funds are enforced by different contracts wired to each other through aragonOS’s ACL system. This architecture allows projects to fine-tune their emergent organization’s governance model and developers to build upon our library to develop additional fundraising modules. We already intend to extend our libraries with some modulation of incentive structures and prevention of pump and dump through token locking.

The tap mechanism will also be complemented by different discreet withdrawal methods (actually, a fee system is already implemented in the market-maker contract) bringing organizations one step closer to automation. Beyond our fundraising library, aragonOS’ modular permissions system enables powerful organization designs that can also depart from the simple model exhibited above: you’ll soon be free to connect Aragon Fundraising to That Planning Suite’s project management apps, a pando/git repository, or the upcoming Futarchy app!

Preventing front-running attacks
The Aragon Fundraising app addresses the critical issue of front-running in bonding curves and decentralized exchanges, where an adversarial actor (typically a miner) can see a large transaction incoming and spends more gas to fill in a faster order. The bonding curve contract is the first implementation of a batched bonding curve conceived by our own Billy Rennekamp. By batching orders and pricing them at a Common Clearing Price front-running is prevented. As a beneficial side effect mass exits are able to occur at a uniform price.

However this also provides a UX challenge in that only estimations of price can be provided to the user. If the user in question is the only order over a span of blocks the price will be accurate. If there is another order with the same intention the price for both will be the same or a little worse than estimated. If another order with the opposite intention occurs, both prices will be better than the estimated. These discrepancies can be mitigated by providing a constantly updated price estimate based on the most up-to-date data from the chain. This becomes much easier to achieve by implementing a robust caching solution using The Graph protocol.

Coming soon
Aragon Fundraising reduces barriers to collaboration. It enables organizations to raise capital while granting contributors a clear set of associated rights and privileges. As a user it makes it easy to join and participate in a decentralized organization, and as an organization it provides a framework for attracting and rewarding contributors.

Fundraising will soon launch on the Rinkeby testnet and, pending completion of security audits, will be released this summer on the Ethereum mainnet. While the upcoming release will be public we will also be supporting a few select projects pre-release.

If you are interested in using Aragon Fundraising please drop us a line or fill out this form.

Thanks to Alexandre Rouxel, Billy Rennekamp, Cem F Dagdelen, Cory Dickson, Daniel Shavit, John Light, Luis Cuende, Luke Duncan, Maria Gomez, Nolwenn Jollivet, Olivier Sarrouy, and Owi Sixseven for contributing to this post.

Last year, we started organizing All Aragon Devs calls to coordinate development work between contributors to the various Aragon software repositories.

On these calls, we discuss everything dev-related from syncing up on what has happened since the last call to work on upcoming sprints to open questions and challenges that might need input from other developers. If any breaking changes are planned, we make sure the relevant stakeholders are aware of these plans so nothing breaks unexpectedly.

Since the first meeting, we have been keeping notes from these calls so we can keep track of progress and the discussions that happened over time. We now have a section of the Aragon Wiki dedicated to organizing information about past and future All Aragon Devs calls.

You can find the archive of meeting notes starting with All Aragon Devs #1 here and information about how to join future calls if you have a topic to discuss with Aragon developers here.

After a few months of organizing these calls privately, we put the infrastructure in place to begin recording the calls and livestreaming them for the wider community to see and stay informed of the latest development activities happening.

A link to the livestream of the next call is shared in the Aragon Chat #dev channel and via the @AragonProject Twitter account when the call is starting.

The next call as of the time of this publishing is scheduled for Monday, May 13th at 15:00 UTC and repeats every other week at the same time after that.

If you’re interested in following the progress of Aragon development we invite you to watch the livestream, and if you have something to discuss with the devs, you are welcome to propose your topic!

On April 27, 2019, Aragon Network Vote #2 concluded.

Nine Aragon Governance Proposals (AGPs) were approved by the Aragon Association Board of Directors to go on to the final ballot. Six AGPs were ultimately approved and three were rejected by ANT holders in this vote cycle.

Here are the final results from Aragon Network Vote #2.

Approved

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-40: Aragon Cooperative DAO funding proposal

AGP-43: ANSP Engagement Policy

Rejected

AGP-37: Retainer for Ongoing Aragon Network Security Provider

AGP-41: Aragon Portfolio Diversification - Acquisition of DOTs

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

Verifying the vote
You can double-check the results of this vote yourself in the governance.aragonproject.eth organization on Aragon.

Feedback welcome

In the spirit of data-driven improvement, we invite all members of the Aragon community, voters and non-voters alike, to fill out a brief, six-question survey and give us feedback that will help us improve future Aragon Network votes. Anonymous results from the survey will be made public for the benefit of everyone interested.

Survey link: https://www.surveymonkey.com/r/YPH7DYZ

Preparing for the next Aragon Network Vote

With this Aragon Network vote behind us, it’s now time to start preparing for the next vote.

The date of Aragon Network Vote #3 is scheduled to start July 25, 2019 at 16:00 UTC, and the deadline for finalizing AGP drafts before the Aragon Association review is July 11, 2019 at 16:00 UTC.

This gives Aragon community members about two and a half months to prepare AGPs before the next vote. Check the Governance page in the Aragon Wiki for updates about Aragon Network vote scheduling and proposal deadlines in case there are any emergency changes. You can also subscribe to the low-volume Aragon Network Vote Alerts mailing list to receive important announcements straight to your inbox.

For complete details about how to make an Aragon Governance Proposal of your own, please review AGP-1, which defines the official process end to end. There are also links to additional resources about the AGP process on the Governance page in the Aragon Wiki. You can ask any questions you have about the Aragon governance process on the Aragon forum or Aragon Chat. And if you have an idea for an AGP that fits into one of the tracks defined in AGP-1, you are invited to start an Aragon forum thread in the Community category using the AGP tag so that Aragon community members can give you feedback about your proposal.

Congratulations and thanks

Congratulations to the authors of the proposals approved in this vote, and thank you to the AGP authors, reviewers, editors, contributors, and everyone who voted for participating in Aragon Network Vote #2 and helping to decide the future of the Aragon project! We look forward to seeing what the future holds for the next Aragon Network vote.

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

Read on for instructions about how to participate in the vote.

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 (approximately) 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:

https://mainnet.aragon.org/#/governance.aragonproject.eth/0x277bfcf7c2e162cb1ac3e9ae228a3132a75f83d4

Note that as one of the oldest Aragon organizations on the Ethereum mainnet, governance.aragonproject.eth may take 10-20 mins to load depending on how fast the nodes you're connected to are. If you experience any issue viewing the open votes for Aragon Network Vote #2, please give the app time to load.

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.

You can find more detailed instructions for how to 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.

If you run into any trouble voting, check the troubleshooting section of the Aragon User Guide, and if the Aragon client continues to not work for any reason then try voting with the raw transaction data below.

Raw vote transaction data

If you are voting from an offline wallet using MyCrypto or another tool for signing raw transactions, you will need the raw vote transaction data below. If you have any trouble connecting to the default node used by the Aragon client, you can also use the raw transaction data below to cast your vote using MyCrypto with any of the supported signing options.

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

Raw transaction YES vote:

To address: 0x277bfcf7c2e162cb1ac3e9ae228a3132a75f83d4
Value: 0 ETH
Data:
0xdf133bca000000000000000000000000000000000000000000000000000000000000000700000000000000000000000000000000000000000000000000000000000000010000000000000000000000000000000000000000000000000000000000000000
Gas limit: 120000

Raw transaction NO vote:

To address: 0x277bfcf7c2e162cb1ac3e9ae228a3132a75f83d4
Value: 0 ETH
Data: 
0xdf133bca000000000000000000000000000000000000000000000000000000000000000700000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
Gas limit: 120000

AGP-28: Decentralizing aragonpm.eth

Raw transaction YES vote:

To address: 0x277bfcf7c2e162cb1ac3e9ae228a3132a75f83d4
Value: 0 ETH
Data:
0xdf133bca000000000000000000000000000000000000000000000000000000000000000800000000000000000000000000000000000000000000000000000000000000010000000000000000000000000000000000000000000000000000000000000000
Gas limit: 120000

Raw transaction NO vote:

To address: 0x277bfcf7c2e162cb1ac3e9ae228a3132a75f83d4
Value: 0 ETH
Data: 
0xdf133bca000000000000000000000000000000000000000000000000000000000000000800000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
Gas limit: 120000

AGP-34: Flock Funding for Aragon Black

Raw transaction YES vote:

To address: 0x277bfcf7c2e162cb1ac3e9ae228a3132a75f83d4
Value: 0 ETH
Data:
0xdf133bca000000000000000000000000000000000000000000000000000000000000000900000000000000000000000000000000000000000000000000000000000000010000000000000000000000000000000000000000000000000000000000000000
Gas limit: 120000

Raw transaction NO vote:

To address: 0x277bfcf7c2e162cb1ac3e9ae228a3132a75f83d4
Value: 0 ETH
Data: 
0xdf133bca000000000000000000000000000000000000000000000000000000000000000900000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
Gas limit: 120000

AGP-35: Edgeware Lockdrop Participation

Raw transaction YES vote:

To address: 0x277bfcf7c2e162cb1ac3e9ae228a3132a75f83d4
Value: 0 ETH
Data:
0xdf133bca000000000000000000000000000000000000000000000000000000000000000a00000000000000000000000000000000000000000000000000000000000000010000000000000000000000000000000000000000000000000000000000000000
Gas limit: 120000

Raw transaction NO vote:

To address: 0x277bfcf7c2e162cb1ac3e9ae228a3132a75f83d4
Value: 0 ETH
Data: 
0xdf133bca000000000000000000000000000000000000000000000000000000000000000a00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
Gas limit: 120000

AGP-37: Retainer for Ongoing Aragon Network Security Provider

Raw transaction YES vote:

To address: 0x277bfcf7c2e162cb1ac3e9ae228a3132a75f83d4
Value: 0 ETH
Data:
0xdf133bca000000000000000000000000000000000000000000000000000000000000000b00000000000000000000000000000000000000000000000000000000000000010000000000000000000000000000000000000000000000000000000000000000
Gas limit: 120000

Raw transaction NO vote:

To address: 0x277bfcf7c2e162cb1ac3e9ae228a3132a75f83d4
Value: 0 ETH
Data: 
0xdf133bca000000000000000000000000000000000000000000000000000000000000000b00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
Gas limit: 120000

AGP-40: Aragon Cooperative DAO funding proposal

Raw transaction YES vote:

To address: 0x277bfcf7c2e162cb1ac3e9ae228a3132a75f83d4
Value: 0 ETH
Data:
0xdf133bca000000000000000000000000000000000000000000000000000000000000000c00000000000000000000000000000000000000000000000000000000000000010000000000000000000000000000000000000000000000000000000000000000
Gas limit: 120000

Raw transaction NO vote:

To address: 0x277bfcf7c2e162cb1ac3e9ae228a3132a75f83d4
Value: 0 ETH
Data: 
0xdf133bca000000000000000000000000000000000000000000000000000000000000000c00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
Gas limit: 120000

AGP-41: Aragon Portfolio Diversification - Acquisition of DOTs

Raw transaction YES vote:

To address: 0x277bfcf7c2e162cb1ac3e9ae228a3132a75f83d4
Value: 0 ETH
Data:
0xdf133bca000000000000000000000000000000000000000000000000000000000000000d00000000000000000000000000000000000000000000000000000000000000010000000000000000000000000000000000000000000000000000000000000000
Gas limit: 120000

Raw transaction NO vote:

To address: 0x277bfcf7c2e162cb1ac3e9ae228a3132a75f83d4
Value: 0 ETH
Data: 
0xdf133bca000000000000000000000000000000000000000000000000000000000000000d00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
Gas limit: 120000

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

Raw transaction YES vote:

To address: 0x277bfcf7c2e162cb1ac3e9ae228a3132a75f83d4
Value: 0 ETH
Data:
0xdf133bca000000000000000000000000000000000000000000000000000000000000000e00000000000000000000000000000000000000000000000000000000000000010000000000000000000000000000000000000000000000000000000000000000
Gas limit: 120000

Raw transaction NO vote:

To address: 0x277bfcf7c2e162cb1ac3e9ae228a3132a75f83d4
Value: 0 ETH
Data: 
0xdf133bca000000000000000000000000000000000000000000000000000000000000000e00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
Gas limit: 120000

AGP-43: ANSP Engagement Policy

Raw transaction YES vote:

To address: 0x277bfcf7c2e162cb1ac3e9ae228a3132a75f83d4
Value: 0 ETH
Data:
0xdf133bca000000000000000000000000000000000000000000000000000000000000000f00000000000000000000000000000000000000000000000000000000000000010000000000000000000000000000000000000000000000000000000000000000
Gas limit: 120000

Raw transaction NO vote:

To address: 0x277bfcf7c2e162cb1ac3e9ae228a3132a75f83d4
Value: 0 ETH
Data: 
0xdf133bca000000000000000000000000000000000000000000000000000000000000000f00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
Gas limit: 120000

What this data means (example)

We believe that everyone should be able to use decentralized organizations. That's why making them easy and secure matters.

Bella is the easiest-to-use Aragon release to date. Let's discover why.

Call people by their name

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.

We have introduced a powerful identity system. In the future, you will be able to plug in many different identity providers, like 3Box.

But with Bella, we 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.

Mobile. Now

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

We released a mobile-compatible alpha version of Aragon at AraCon 2019. Since then, we 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.

Upgrade everything

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. We want to make sure that your organization is fully sovereign.

Keep track of your activity

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?

Now, you will always know.

Payroll becomes easy (invite-only)

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. Until then, we will test Aragon Payroll with a handful of selected organizations. If you are interested, please reach out.

Constantly improving

There are also many minor fixes and improvements.

We are listening to users and collecting feedback. We want to make Aragon the dream way of running organizations of the future.

Do you want to help us on this journey? Check out job openings at Aragon One and Autark.

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.

In January 2019 the Aragon community gathered in Berlin for the first AraCon - the Aragon community conference.

With many talented members of the community sharing progress on their projects and their visions for the future of Aragon, Ethereum, governance, and the decentralized web, a lot of great content was produced from this event.

For those who couldn’t make it, missed some of the action, or just want to relive some of the experience, we now have an AraCon 2019 photo gallery on the Internet Archive and a video playlist of all presentations and panel discussions on the Aragon Project YouTube channel for your viewing pleasure.

Dreaming of AraCon 2

The first edition of AraCon was barely over before we began receiving questions about when and where the next Aragon conference will be. The answer is that we don’t know yet! We haven’t started planning it. What this means is that you still have an opportunity to shape the next AraCon event.

If you want to help us dream up ways of making the next AraCon even better than it was this year - a tall task based on the wonderfully positive feedback we have received so far - then we invite you to take our survey to review your experience at AraCon this year and share your ideas about what new experiences we can co-create at the next one.

Take the survey here to give your feedback directly to the AraCon organizers. You can start a thread in the Aragon Forum if you want to discuss your ideas with the community as well. The survey results will feed back directly into the organizing process for the next AraCon, so we greatly appreciate and value every response.

Thank you to everyone who made AraCon 2019 an amazing success

The event exceeded our expectations in every way, and we couldn’t have done it without the help and support from our organizing team, production crew, venue and catering staff, satellite event and afterparty hosts, DJs, speakers, MCs, volunteers, and everyone else who helped along the way. And of course, a big thanks to everyone who joined us, new and old friends alike, for this special occasion. We hope to see you again at another Aragon event soon!