This is our regular monthly progress report for Autark and Open Work Labs' work on AGP-19, which was funded via Aragon Network Vote #1. This post is broken down into the initiatives in our original proposal.
First, we wanted to share a visual of our initiatives. The dark grey bottom layer depicts focus areas that the blocks immediately above, in the light grey layer, are “consuming”.
Initiatives I01 and I05 are parallel efforts to I02, I03 and I06. For example, the Organization Identity initiative requires a Data Storage solution for user generated data, and it also is dependent on enhancements to the Aragon client that will technically fall under the Cross App UX initiative -- such as how data is shared between applications.
I01 - Cross-Application User Experience
Based on development survey results and our own experience developing Aragon apps, we published a forum post that describes features that will be important to enhance the user experience for Aragon users.
After further review, we have decided to prioritize the development work based on our other initiatives that are dependent on these enhancements. Hence our initial focus will be areas that are related toward the Organization Identity initiative.
Read more in the I06 section of this update for details.
I02 - Contextual Discussions
As mentioned in our March update, we completed the technical spec for discussions. This month there has not been any development work directly related to discussions, although there has been dependent work that this initiative is consuming from the Data Storage initiative. Read more in the I05 section of this update for details.
We plan on beginning Discussions application development work after completing the Profiles initiative.
I03 - Rich User Profiles
We began development of the Profile app and completed the 3box integration; right now we are building out the remaining frontend features.
To support this effort, we submitted 3 PRs to Aragon repositories to integrate signing arbitrary message into Aragon, in attempt to make Profiles compatible with 3box:
There is still some more work to be done to resolve iframe sandboxing security restrictions, in order to become compatible with OrbitDB (which 3box utilizes).
While we began the prototype as an app, we think that profiles should be included in the Aragon client, as the MVP of a user profile is organization-agnostic. We plan to present our case for this in the coming weeks.
I04 - Expanding Governance
This is an initiative that expands upon our Planning Suite work by providing more features for reputation/merit based organizations, and we are in the process of planning the development timeline for the quasi-transferable token solution which is the core of this initiative.
This month we did develop a template for the Planning Suite and once we complete quasi-transferable tokens, it will be really easy to modify it to support the DAO Template aspect of this initiative.
I05 - Data Storage and Standards
We began to share research and ideas on the forum related to IPFS pinning and querying -- and this impacts three of our initiatives (I02, I03, I06) that rely heavily on user-generated data in different ways.
Our Flock proposal mentioned intermediate caching solutions, and hence we developed the beginnings of a backend REST API that pins files and metadata to IPFS and stores information in Mongo. The file adding, dag putting, pinning functionality, and Mongo storing are working. We’ve backseated this API for now as the discussions on IPFS Pinning solutions mature into an action plan.
I06 - Organization Identity
Whenever we initially proposed the Organization (DAO) Identity initiative we had described there would be an “About app” to manage various data blobs such as a manifesto, mission statement, etc. Although in the past month, we began to make the case that instead of a separate About app, that this should instead be the Home app.
We received buy-in from Aragon One on this high level strategy and in the past few weeks we have been starting to share design and technical research to receive buy-in for the ultimate implementation.
We delivered an initial design concept which presents a widget-based approach for customizing an organization’s homepage. In order to accomplish this, we need the ability to: pull individual application state into the client, store information about the home app, interpret information pulled from individual applications, and provide information back to individual applications. Refer to the technical architecture proposal for some initial ideas.
I07 - Rewards Application and Planning Suite
Last month we were in the middle of the application development for the Rewards application, with the integration between the front-end and smart contracts remaining, and this month we completed the development.
Reward distributions can now be created using an snapshottable reference token that conforms to the Minime function signature. Rewards can also be created and calculate retroactively (so long as they don’t predate the creation of the reference token).
We completed making all of our applications responsive. We got fully acquainted with the process of publishing applications and updated our application manifests to conform to the new app center standards with screenshots, simple descriptions and icons that are complementary to the other Aragon core apps.
We launched That Planning Suite on Rinkeby and created a demo Dune DAO that comes with our apps installed.
We developed a template to create a Planning Suite DAO, basing it off the Democracy and Beta Base templates, and also integrated it with a frontend to make it really easy for people create a Planning Suite DAO without touching the cli. This resulted in us spinning up a server to host a version of the client at rinkeby.autark.xyz. We did also create a guide for people that are interested in installing the apps individually via the cli.
While we are on Rinkeby now, there is always room for improvement. Our next steps are to finish implementing end to end testing, perform QA for cross browser compatibility, address bugs reported by alpha users, perform a thorough internal code review and audit, lock down our contracts so we can then hand it off for an external security audit, and make adjustments as necessary for our mainnet release.
Period: March 23, 2019 — April 30, 2019
- DAI: 21,194.30 DAI
- Fiat: $112,315 USD
Total: $133,509.30 USD (assuming 1 DAI = 1 USD)
- Autark Payroll (3 pay periods): $63,622.00
- Open Work Labs Payroll (3 pay periods + overtime): $17,144.52
- Reimbursed Expenses (co-working spaces, software licenses, etc.): $1,096.49
- Misc Transaction/Currency Conversion Fees: $340
- Fiat: $30,121.99 USD
- DAI: 21,184.3 DAI
Total: $51,306.29 USD
Verify: $133,509.30 (previous balance) - $82,203.01 (costs) = $51,306.29
- $82,203.01/1.5 = $54,802/month
- $27,401 per pay period (2x a month)
The remaining balance will cover our next pay period and upcoming costs such as our offsite and new hire. We are expecting to receive our second tranche of $195,000 in mid-May to ensure steady operations.
Our burn rate will increase as soon as we onboard a person for the frontend engineer position that we have been actively recruiting.