Progress of development from the first quarter of 2018
Releasing Aragon Core v0.5, The Architect, was the biggest development milestone during the first quarter of the year. For some more information on the actual launch, you can check the official announcement:
It is worth noting that there is not a single line of code in Aragon Core v0.5 being reused from the previous releases. This release is a full DApp (served using IPFS); we have discontinued the native desktop clients for the time being.
We separated the JS library that is used to interact with Aragon DAOs to its own package, this allows for easily creating different clients (different UIs, mobile apps or CLIs)
Loads the state of an organization, its different apps and ACL permissions from the blockchain.
Cache state locally for quicker and leaner loads.
Support for aragonOS transaction pathing, which allows users to directly invoke an action on an app, even if they don't hold the required permissions themselves, and it will calculate what needs to happen (e.g create a vote).
Radspec integration for describing transactions in a human-readable form.
Our design framework with React components that are used to build the wrapper and our own Aragon apps.
Implementation of new components, totalling at 24 components that have been released with this version: *AragonApp, Badge, BadgeNumber, BaseStyles, Button, Card, CircleGraph, ContextMenu, Countdown, DropDown, Field, Footer, HOC, Header, IllustratedSection, Info, Input, LayoutGrid, Link, PreFooter, Radio, Section, SidePanel *and Table.
External third party apps are already using aragon-ui for non-Aragon apps like tcr-ui.
DApps that can be shut down by shutting down a company's servers are not decentralized apps, just normal web 2.0 apps that use Ethereum as a settlement layer. This is certainly an improvement from using a centralized payments or database provider, but these apps could still be instantly stopped if a powerful enough actor feels threatened by it.
We feel very strongly about Aragon Core being a true decentralized app,resistent to censorship, no matter who doesn't like a given organization or Aragon app, it should be up to each individual to decide whether they want to use it or not. This applies to Aragon itself, no matter if the team disappears overnight or if we are asked to shut down Aragon Core or a particular organization, we have architected the system to not have such power.
However, given the current state of the decentralized web infrastructure, we had to make some trade-offs to ensure our beta could be used by anyone with as little friction as possible.
aragonpm.com: aragonpm.com runs apm-serve which is our easy to use bridge from web 2.0 to APM. When requesting aragon.aragonpm.com, apm-serve fetches the APM package at aragon.aragonpm.eth , along with the latest version of the content from IPFS and serves it through HTTP(S). We will be working on making it easier to run apm-serve locally and not require using our server for this.
Metamask (and therefore Infura): we made Metamask the default, easy way to use Aragon Core. This results in using trusted nodes by Infura as default.
It is worth noting that during our testnet beta, there is certainly less at stake than once we go to Mainnet. We are working on ways to easily create trustless local setups for people to use Aragon Core without relying on any piece of centralized infrastructure.
We always appreciate community contributions, so a big thank you to all the community members who contributed during Q1!
To incentivize more community contributions, we also have some bounties posted that are free for anyone to submit a claim to! We will also be posting more in the next quarter, so make sure to check back!