Releasing Aragon Agent beta by Jorge Izquierdo (Co-founder Aragon Project, CTO Aragon One) — a new app that enables Aragon organizations to interact with any Ethereum contract or protocol.

Aragon Agent is a fully-fledged Ethereum account owned by an Aragon organization. It’s like a multi-signature account on steroids that enables organizations to interact with any Ethereum contract or protocol. Trading tokens on 0x or Uniswap, opening a Maker CDP, managing names in ENS, owning digital LAND parcels, or even breeding digital cats.

Before Agent, those interactions required taking funds out of the organization and sending them to a trusted operator. Then the operator would interact with the external contracts, and return the assets to the organization afterwards. With Agent, this can be done within the organization in a completely trustless way.

Agent also allows organizations to interact with other organizations, opening up an incredible amount of experimentation with inter-organization interactions.

An Agent represents one identity of the organization. For the external world, the Agent identity is static, even after upgrades to the governance process of the organization. This removes the need for painful migrations after governance changes.

The best way to build deep integrations with other protocols is still building an Aragon app with aragonSDK. But Agent introduces a great way to interact with external contracts without the need for building a custom Aragon app.

Applications and contracts on Ethereum have lots of different use cases and user targets. That’s why Aragon team decided to push three different interaction models for Aragon Agent:

aragonCLI Agent support (beta) Web3 signer integrations (coming soon) Agent webapp (coming soon)

Moloch DAO & Permissioned DAOs by Yalda Mousavinia.

Aragon Greta DAO by Gustav Marwin.

Cooperative DAO Governance — Models,Techniques & Proposals by Julian Brooks.

Developer relations opening application; Is this hiring@aragon.one? Just kidding by Tommy Cox.

Preparing for Polkadot.

Updates from Aragon chat (12th February — 26th February):

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

- Continue working on 2 or 3 blog posts

- A1 goals tracking and tasks cleanup

- Supporting next A1 offsite planning

- Enhancing product dev cycles at A1

- Multiple operational tasks

- Write and review blog posts

@jorge (Jorge Izquierdo, CTO at Aragon One):

- Release Agent https://github.com/aragon/deployments/pull/43

- Started working on the radspec registry for non-Aragon contracts

- Some contributions to aragon/aragon and aragonCLI to support the Agent release

- Kleros Aragon Court: auditing the Kleros protocol

- Agent release blog post

- Work on my research writing backlog: Aragon Chain, Voting v2 contract arch, Metadata DAO

- Released Aragon Agent 🎉

- Aragon Court: started implementing from scratch (general court state machine working!)

- Aragon Court: implement dispute creation, voting, appeals

- Voting v2: prepare ETHCC presentation and write about new voting arch

@lkngtn (Luke Duncan, Research at Aragon One):

- Review @bingen ‘s delegative voting spec

- Test and document Agent app + Openlaw flow on rinkeby

- Work on Aragon Network communications plan

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

- More communications documentation

- Publishing upcoming blog posts

- GitHub organization / governance documentation

- Finished governance comms plan

- Drafted review of ANV-01

- Reviewed and published the Agent post

- Worked on Q1/Q2 events planning

- Continue with Q2 events planning

- Start planning for ANV-02

- Work on upcoming blog posts

@jounih (Jouni Helminen, Design at Aragon One):

-New preferences layout (full screen modal)

- More discoverable preferences

- new sections for App menu panel

- Custom label preferences screens for desktop + mobile

- Aragon Figma housekeeping

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

- New job description

- Hiring: screenings, interviews

- People ops: contracts, amendments, equipment

- HR Strategy: Planning Offsite #5, coaching

- @danielnorman’s onboarding: Welcome to the team :frogdance:

- Misc HR ops

- Research travel agency

- Close offsite #5 partner + offsite prep

- New payroll policy + prepare payroll part I

- Interviewing potential candidates

- Coaching + help with internal ops

Planned for this week:

- Offsite planning

- Travel agency partnership and coordinate next itineraries

- February compensation + expenses

- Hiring: follow-ups and technical challenges + usual coaching sessions

- Internal ops

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

- Agenda Management

- Travel arrangements

- Accounting & payments

- Other administrative and legal tasks & follow-ups

@bpierre (Pierre Bertet, UI & Interaction Developer):

- App Center

- PRs reviews: aragonUI + aragon/aragon

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

- Support Agent app beta pre-release

- Modernize Survey app and planning its re-release

- Sync with AGP security partners on next steps and priorities

- Support Aragon 0.6.4 development, to be release next week!

- Kickoff A1 sprint 4.2

- Release Aragon 0.6.4

- Deploy smart contract upgrades for Aragon 0.6

- Helping @danielnorman onboard!

- Pushed 0.6.4 release to next week, so we can get a few more fixes and changes in for the Agent app

- Working with the Security Partners to have a smooth contract upgrade soon

Planned for this week:

- Release Aragon 0.6.4 (for real!)

- Write local identity data spec, and more generic “identity provider” spec for other methods of resolving addresses to metadata

- Review Staking and Payroll

- Review TPS’s 3rd milestone

@bingen (Bingen Eguzkitza, Solidity Engineer):

- Review some PRs from aragon-apps, dao-kits and aragonOS

- Nest: support and review a couple of projects

- Review Single Delegation spec comments

- Review and iterate over Jorge’s Sum Tree sortition implementation

- Devops: help setting Nextcloud app

@delfi (Delfina Polito, Frontend at Aragon One):

- AraCon post-event changes on website

- Aragon public roadmap for website

- Finished second iteration of developers portal redesign

- Deployed public roadmap to Aragon website

- Polish preject’s blog

- Closed some issues on Aragon website

- Started with forum themes redesign

- Continue with what’s left of forum redesign (light and dark themes)

- Update mailing list on Aragon One blog

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

- Address comments on `responsive` open PRs and get those merged!

- Continue work with thats pending on the second iteration of `responsive`

- Do some research into automated tests for the front-end

- Swipe open/close updates

- `aragon/ui` new components and changes from `responsive`

- Common components for `aragon/aragon` from responsive

- Started work on `Custom labels

- Work on `Custom Labels` view

- Get as much work done on the remaining fixes for `responsive` and merge open PRs

@dizzypaty (Patricia Davila, Product Owner at Aragon One):

– Product sprint planning tasks & calls

– Plan user research at EthCC & Flock teams coordination

– Product on-boarding for new team members

– Agent app scope and flows

@yalda (Yalda Mousavinia):

- Roadmap prioritization

- Sprint planning

- Legal logistics (entity formation for real world interface; accounting)

- QA testing of Milestone 3 from our Nest grant

* Legal and operational logistics for receiving our first payment

* Polished up Rewards app product spec and missing screens; initial braindump of the information architecture for profiles

* Created tickets in Github for Rewards app and other TPS tasks

* Initial brainstorms around EthCC user research strategies

* Roadmap, prioritization, QA testing

Besides my typical PM tasks of testing/sprint planning, etc. Plans for this week:

* Hopefully finalizing banking / finding a bank [getting paid in ETH within hours of market dipping, and not enough DAI on market = not stable :)]

* Prepare slides for my Thursday talk on Autark at Full Node Berlin

* Finalize proposal for EthCC user research questions

* Publish initial draft product spec for Profiles and DAO’s “about” information

@quazia (Arthur Lunn):

This week worked on:

- Defined clear development processes for the team

- Finished back-end front end integration for our Projects app bounty flow including allocations/vault integration/IPFS integration

- Started work on the Rewards App Spec [WIP]

@listenaddress (Thomas O’Brien):

- Got good idea of methods/data for profile, discussions and about section.

- Researched 3Box, OrbitDB, and Textile. Began conversations with those teams.

- Got 3Box-linkedin demo and simple auth server going.

- Reviewed Aragon and espresso code and documentation. Began tinkering.

@danielnorman (Daniel Norman):

- Read the whitepaper

On-boarding tasks

Goal setting

Techincal onboarding with the help of @sohkai

(wip) rxjs upgrade testing/review

- Continue on technical onboarding

- `aragon.js` — support the rxjs upgrade

- `aragon.js` — review/test other blocking PRs

- `aragon.js` — Rebase and continue on ACL caching PR

@gabi (Gabriel Garcia):

- Worked on e2e test for aragonCLI

- Looked hack.aragon/forum/chat/codebase gathering information to update aragon CLI documentation. Created this document to write ideas and necessary changes, any feedback is welcome.

- Help release `@aragon/cli@5.4.0-beta.1` 🚀

- Gave support to new users

@kevin.siegler (Kevin Siegler):

- Review @yalda ‘s spec for the rewards app

- Implement and test the frontend/backend integrations to finish up the projects app

@rkzel:

Projects app:

- front end

- back end integration of Projects app (web3, ipfs)

- polish up code for other apps in the Planning Suite (our Milestone 5 work which rolled into Flock)

@jon:

- Figure out what needs to be stored for profiles and discussions.

- Research distributed DBs including Textile, OrbitDB, 3box. We’ve started conversations with these three groups.

- Start poking around Aragon’s IPFS node setup, aragon-datastore, and the projects app.

This week for Open Work Labs:

- Finish proof of concept app that integrates 3box and linkedin

- Write up research on 3box

- Start working on a POC with textile cafes

- Write up research on textile

- Start forming a proposal about what tools to use (3box, textile, caching server…etc) for profiles / discussion features

- Start gathering relevant open data standards