<h3>Goals</h3>
<ul>
<li>Start transitioning Aragon’s governance from a highly centralized model to a more decentralized one</li>
<li>Experiment with community participation while still ensuring the safety of the project</li>
<li>Document and formalize this new process so governance stakeholders can be kept accountable</li>
</ul>
<h3>Description</h3>
<p>Right now the governance of the project is fairly simple:</p>
<p></p><div><a href="https://global.discourse-cdn.com/standard14/uploads/aragon/original/1X/c95552c7c739489e3d055216648c1d9393d5d106.png"><div><span>Screenshot_20180723_144541</span><span>991×351 18.2 KB</span></div></a></div><p></p>
<p>Using the following components, I propose an structured process to start decentralizing governance:</p>
<ul>
<li>The <a href="https://survey.aragon.org">Survey app <span>16</span></a>, which lets the DAO query ANT holders with non-binding votes</li>
<li>The <a href="https://wiki.aragon.one/dev/apps/finance/">Finance app <span>13</span></a>, which lets the DAO keep track of finances and propose new transactions</li>
<li>The <a href="http://wiki.aragon.one/dev/apps/voting/">Voting app <span>10</span></a>, which lets ANT holders vote on binding votes (such as approving or proposing new transactions in the Finance app)</li>
<li>
<a href="https://github.com/floating/frame">Frame <span>19</span></a>, which lets anyone vote using hardware wallets</li>
</ul>
<p>Let’s divide governance decisions into two groups:</p>
<ul>
<li>Binding: Governance decisions taken by stakeholders are automatically enforced by code or legal contracts</li>
<li>Non-binding: Governance decisions taken by stakeholders are not automatically enforced by code and need humans to actually perform the outcome desired by the stakeholders</li>
</ul>
<p>Since this is a proposal for kickstarting decentralized governance, we still need to keep safety measures in case any possible attack or malfunction happens in the governance system or voting mechanism.</p>
<p>That’s why I would like to propose a mechanism in which:</p>
<ul>
<li>The Aragon Association (previously called Foundation), the legal entity that has power over the project, still has power to make governance proposals
<ul>
<li>Either proposes to perform a direct action (like spending funds, or updating legal terms)</li>
<li>Or proposes to appoint some entity (a delegate) that will act in behalf of the project (like appointing someone to manage the grants program or the social media channels)</li>
</ul>
</li>
<li>But ANT holders have power to veto those proposals
<ul>
<li>If ANT holders veto a delegate nomination, the Association must propose different delegates</li>
<li>If ANT holders veto a proposal, and it’s clear that there has been an attack on the voting mechanism, the <a href="https://wiki.aragon.one/documentation/multisigs/community/">Community Multisig <span>5</span></a> could veto the veto as a last resort</li>
</ul>
</li>
</ul>
<p>So there would be four types of governance decisions:</p>
<ul>
<li>
<p>Binding</p>
<ul>
<li>With direct veto</li>
<li>With veto over delegate nomination</li>
</ul>
</li>
<li>
<p>Non-binding</p>
<ul>
<li>With direct veto</li>
<li>With veto over delegate nomination</li>
</ul>
</li>
</ul>
<p>Now let’s jump into the actual proposal for decentralizing governance over each component.</p>
<h4>Nest grants</h4>
<h5>Binding, with direct veto over its funding and veto over delegate nomination</h5>
<p>We can transform the Nest grants program into its own DAO.</p>
<p>The funding of that DAO would work as follows:</p>
<ul>
<li>Nest would have a yearly budget approved by the Association</li>
<li>The Association would create the transaction to fund the Nest DAO</li>
<li>ANT holders could veto it</li>
</ul>
<p>And its governance:</p>
<ul>
<li>The Association would propose delegates who would run the program for a year</li>
<li>ANT holders could veto the proposal</li>
</ul>
<h4>Funds</h4>
<h5>Binding, with direct veto</h5>
<p>Thanks to <a href="https://blog.aragon.one/decentralizing-aragons-development-iii-onboarding-new-teams-32786cb805a5">the split between the Association and the development teams <span>3</span></a>, the Association will perform a few monetary transactions per year, therefore making it possible for ANT holders to have direct veto power.</p>
<p>Examples:</p>
<ul>
<li>Giving out a sizable grant to an Aragon development team</li>
<li>Sending money to the Nest grants program</li>
</ul>
<h4>Social media, Aragon Chat</h4>
<h5>Non-binding, with veto over delegate nomination</h5>
<ul>
<li>The Association would propose delegates to run the social media accounts and maintain the Aragon Chat for a year</li>
<li>ANT holders could veto the proposal</li>
</ul>
<h4>Repositories</h4>
<h5>Non-binding, with veto over delegate nomination</h5>
<ul>
<li>The Association would propose delegates to maintain the repos
<ul>
<li>Repos would be software repos but also include the multiple websites that are statically hosted</li>
</ul>
</li>
<li>ANT holders could veto the proposal</li>
</ul>
<p>Next step would be to make this a binding proposal by using <a href="https://github.com/ryhope/pando">Pando <span>7</span></a>.</p>
<h4>Legal terms</h4>
<h5>Binding, with direct veto</h5>
<ul>
<li>The Association would propose versions for
<ul>
<li>The Trademark Policy, that lays out how to use the Aragon brand</li>
<li>The Licensing Policy for significantly changing the licenses of the software or content</li>
</ul>
</li>
<li>ANT holders could veto the proposal, in which case they would remain unchanged</li>
</ul>
<p>In order to make this binding, the Association would sign a legal agreement stating that it will adhere to the results of the votes for updating or not updating these legal docs.</p>
<h3>Technical implementation</h3>
<p>This would be achieved by deploying a DAO (Aragon Governance DAO) with:</p>
<ul>
<li>
<p>A Finance app and a Voting app, for binding decisions</p>
<ul>
<li>The Voting app should require high enough parameters in order to really gauge community discontent. This could be:
<ul>
<li>25% quorum, so 1/4 of ANT holders would have to vote</li>
<li>51% support, so more than half of the votes are required for a veto to happen</li>
</ul>
</li>
</ul>
</li>
<li>
<p>A Survey app, for non-binding decisions</p>
<ul>
<li>We would need to state the amount of votes that we would consider for a veto</li>
<li>As the app is multi-option, each delegate could have its own option, so holders could veto one of the delegates but not the others
<ul>
<li>We could say that in order to veto a delegate, 10% of ANT are required to veto</li>
</ul>
</li>
</ul>
</li>
<li>
<p>Describe some unsolved problems or points of discussion, if there are any.</p>
</li>
</ul>
<h3>Uncertainties</h3>
<p>As with any token-based voting mechanism, there can be perverse incentives so holders want to veto proposals for their short-term benefit. I believe this is mitigated by making veto the first step, and not full control, therefore giving the Association the power to propose.</p>
<p>Also this should be seen as a transition state, until we have the research and experience in place to give ANT holders full control over the Aragon Governance DAO.</p>

Decentralizing Aragon’s governance: Possible first steps Goals 
 
 Start transitioning Aragon’s governance from a highly centralized

Decentralizing Aragon’s governance: Possible first steps

<h1>Aragon Roadmap</h1>
<p>I wanted to write some <strong>raw thoughts</strong> on the Aragon roadmap. The points are ordered by priority, although don’t take this as any formal roadmap whatsoever.<br />
This is <strong>just a brain dump</strong> of items that I consider relevant for the success of Aragon. I <strong>intentionally excluded other very important apps</strong> for Aragon, such as the TCR or Liquid Democracy. I wanted to only include here fundamental features and apps that make Aragon a great platform to build dapps and create DAOs, and not the actual apps that will likely be built on top and drive usage.</p>
<h2>Permissions</h2>
<p>Allow users to visualize who has control over the resources of a DAO, and modify those permissions too.</p>
<p>Relevant issues: <a href="https://github.com/aragon/design/issues/6">https://github.com/aragon/design/issues/6 <span>3</span></a></p>
<h2>Entity component</h2>
<p>Human-readable names are important. We should provide a UI component to visualize:</p>
<ul>
<li>
<p>ENS names</p>
</li>
<li>
<p>Aragon apps</p>
</li>
<li>
<p>Aragon DAOs</p>
</li>
<li>
<p>Known contracts, including tokens (maybe using the MyCrypto list)</p>
</li>
<li>
<p>Plain Ethereum addresses</p>
</li>
</ul>
<p>This component should be a part of Lorikeet and easily embeddable by developers.</p>
<p>Relevant issues: <a href="https://github.com/aragon/aragon-ui/issues/156">https://github.com/aragon/aragon-ui/issues/156 <span>1</span></a> and <a href="https://github.com/aragon/design/issues/3">https://github.com/aragon/design/issues/3 <span>1</span></a></p>
<h2>Aragon ID</h2>
<p>Aragon ID lets users and DAOs have rich metadata over their identities. That data can be exposed via the Entity component.</p>
<p>Relevant issues: <a href="https://github.com/aragon/design/issues/5">https://github.com/aragon/design/issues/5</a></p>
<h2>Actor app</h2>
<p>The Actor app would let DAOs interact with external contracts that don’t follow the aragonOS interface.</p>
<p>Relevant issues: <a href="http://forum.aragon.org/t/dynamic-permissions-for-organization-actions-with-signer-integration/116">Dynamic Permissions for Organization "Actions" with Signer Integration <span>1</span></a></p>
<h2>Responsive</h2>
<p>Aragon Core should be responsive to work on mobile. This needs:</p>
<ul>
<li>
<p>For all the apps to be responsive</p>
</li>
<li>
<p>For the left sidebar to be hidden by default</p>
</li>
</ul>
<p>Relevant issues: <a href="https://github.com/aragon/design/issues/4">https://github.com/aragon/design/issues/4 <span>3</span></a></p>
<h2>DAO chooser</h2>
<p>As Aragon Core supports interacting with multiple DAOs, we could replace the logo on the top left with a DAO chooser that lets you switch to DAOs you have pinned there. It could also leverage Aragon ID and the Entity component to show the DAO metadata, such as name and icon.</p>
<h2>Notifications</h2>
<p>Notifications were a big feature in the pre-0.5 era of Aragon Core. We should re-introduce them. There’s already support for them in part of the frontend and aragon.js. We should let apps show notifications, and also use notifications as a way to track progress of transactions yet to be introduced in a block.</p>
<p>Relevant issues: <a href="https://github.com/aragon/aragon/issues/117">https://github.com/aragon/aragon/issues/117 <span>2</span></a></p>
<h2>App center</h2>
<p>It is very important that users are able to install and uninstall apps from their DAOs. We need to build a minimum viable App center that allows for that.</p>
<h2>Optimistic UI patterns</h2>
<p>Lorikeet should have optimistic UI patterns built in, so developers don’t need to worry about listening for blockchain transactions and re-rendering their app. Users should also feel that their actions happen immediately, whenever possible.</p>
<h2>User-centered Home app</h2>
<p>We should redesign the Home app and add a user-centric view informing the user about actions that they have initiated within the DAO.</p>
<p>Relevant issues: <a href="https://github.com/aragon/aragon/issues/135">https://github.com/aragon/aragon/issues/135</a></p>
<h2>Aragon Network integration</h2>
<p>We should create Aragon apps for the Aragon Network that allow for:</p>
<ul>
<li>
<p>Judges to participate in cases</p>
</li>
<li>
<p>Participants to create agreements and provide collateral for them</p>
</li>
<li>
<p>Participants to provide evidence to judges</p>
</li>
<li>
<p>Users to create their own nested jurisdiction (that we call <em>context</em> in the whitepaper) that inherits from the Aragon Network or any other context</p>
</li>
</ul>

Thoughts on Aragon client roadmap Aragon Roadmap 
 I wanted to write some  raw thoughts  on

Thoughts on Aragon client roadmap

<p>Hey Aragon community,</p>
<p>In the spirit of transparency, I wanted to write some thoughts about the Aragon Network DAO and its future.</p>
<p>I recently proposed <a href="https://forum.aragon.org/t/an-implementation-proposal-for-the-ant-anj-merger-no-lock/2530">a possible way forward for the ANT-ANJ merger <span>4</span></a>, and there were different views by both other community members and Aragon’s co-founder Jorge. I think this is healthy, since decentralized governance cannot happen without public discourse, and I am happy that at least my proposal sparked debate and interest.</p>
<p>As a co-founder, I know my words carry a lot of weight, but I just want Aragon to be successful, so I’m not afraid of withdrawing my proposals if the community comes up with better ones. In fact, I wanted to write this for community members to write their views, even if they are different to mine.</p>
<p>One issue that arose in the ANT-ANJ merger proposal was the ability for the <a href="https://wiki.aragon.org/association/multisigs/community/">Community Multisig <span>3</span></a> to mint more ANT. The idea was always to have the Community Multisig as the placeholder for the Aragon Network DAO. We have been talking about that DAO for a long time, and about giving ANT holders true control. There has always been a technical reason to postpone, whether it was implementing a new feature, refactoring the system, needing more legal research, etc. Being the leading DAO project, our DAO must of course be excellent. But on the other hand, Aragon looks incoherent spreading DAO usage while not dogfooding its own.</p>
<p><a href="https://governance.aave.com/t/arc-add-support-for-ant/1923">A proposal to get ANT into Aave <span>1</span></a> was also published, but Aave’s co-founder Stani expressed his discomfort about the Community Multisig being able to mint more ANT. Not only Aragon looks incoherent, not having its own DAO, but it is also limiting ANT’s adoption. So I think it would be a good moment to introduce a minimum viable DAO for the Aragon Network.</p>
<p>I’d suggest following the model that some communities are taking to progressively decentralize. That would be deploying an Aragon DAO that would have control over minting more ANT, and then have a multisig (which could be a cryptoeconomics committee elected by ANT holders) that can veto minting events. Then ANT holders might choose to, for example, make ANT inflationary with a predictable supply schedule. Or they might choose to instead cap it and follow a <a href="https://www.placeholder.vc/blog/2020/9/17/stop-burning-tokens-buyback-and-make-instead">buyback and make model <span>2</span></a>. Either way, the cryptoeconomics committee could veto decisions, minimizing the risk of 51% attacks or a malicious takeover. Eventually, the DAO might decide to replace the committee and adopt <a href="https://aragon.org/agreements">Aragon Agreements <span>2</span></a>.</p>
<p>While I do think that launching a “perfect” DAO showcasing Aragon Agreements, Aragon Protocol and Aragon Govern would be ideal, if we cannot achieve that in the next few weeks, I would propose just adopting Aragon v1. Then the DAO can always decide to transition minting abilities to a new Aragon v2 DAO once ready.</p>
<p>Again, this is not a fully fledged proposal and it doesn’t intend to be. It’s just a few thoughts to kickstart open discussions, hopefully resulting in proposals by community participants.</p>

Next steps towards the Aragon Network DAO Hey Aragon community, 
 In the spirit of transparency

Next steps towards the Aragon Network DAO

<p>Please use this thread to write a brief of why you want to join the <a href="https://www.notion.so/aragon/Product-Working-Group-e93697ee84724adda73f3029074c3d84">Product Working Group <span>14</span></a>.</p>
<p>To qualify for this working group, you may either:</p>
<ul>
<li>Be either part-time or full-time employed by an Aragon Flock team</li>
<li>Be a recognized community contributor</li>
</ul>

Product Working Group membership thread Please use this thread to write a brief of why

Product Working Group membership thread

<h1>
<a name="summary-1" href="#summary-1"></a>Summary</h1>
<p>This proposal would establish a partnership between Aragon and <a href="https://nation3.org">Nation3 <span>11</span></a>, as a cornerstone to make DeLaw happen and superpower DAOs.</p>
<p>There is already significant ideological alignment and team alignment, and this proposal would take this a step forward by formalizing financial alignment as well. This proposal would also enable Aragon to superpower its offering to DAOs and DAO contributors with legally-binding agreements, while being able to remain laser-focused on DAO tooling and the DAO framework offerings.</p>
<h1>
<a name="details-2" href="#details-2"></a>Details</h1>
<h2>
<a name="introduction-3" href="#introduction-3"></a>Introduction</h2>
<p>When Jorge and I co-founded Aragon back in 2016, we had a vision to make on-chain organizations happen. We realized the potential of creating new kinds of entities that would be fully sovereign, highly efficient, and transparent (when needed).</p>
<p>As we realized over the years, we were too early. Many building blocks needed to be built. When we released Aragon to the public, Dai wasn’t even launched.</p>
<p>Today, DeFi allows DAOs to have access to even better tools for yield and treasury management than those of traditional corporations.</p>
<p>The second building block that we had envisioned for Aragon was a decentralized jurisdiction (think of it as DeLaw). After all, DAOs can run some operations on dry code (smart contracts), but a lot of the human interactions cannot be codified, and must run on wet code (legal contracts).</p>
<p>For that purpose we envisioned Aragon Court — a first-of-its-kind dispute resolution protocol.</p>
<p>We imagined that DAOs could leverage all the best of automation with smart contracts, while also enjoying the granularity of legal contracts collateralized by tokens. And, in the process, we thought we would build the world’s first digital jurisdiction where DAOs are first-class citizens.</p>
<p>Unfortunately, Aragon Court failed. Looking back, its failure was mainly attributed to four things:</p>
<ul>
<li>First and foremost, building core infrastructure for DAOs is a huge undertaking by itself. We were stretched too thin and couldn’t focus on Aragon Court. Which I think was the right call — <em>focusing on everything means focusing on nothing</em>.</li>
<li>Second, dispute resolution cannot exist on its own without a system of law. Whoever is in charge of resolving disputes needs a clear framework to adhere to.</li>
<li>Third, no one wanted to rely on an anonymous jury (random people over the Internet staking tokens) to resolve their disputes. Everyone wanted legal professionals instead. Understandably so.</li>
<li>Fourth, making all agreeements and disputes public (even having to make sensitive evidence public) turned off potential users. No organization wants to make their disagreements public, and of course there’s a big privacy concern for individuals too.</li>
</ul>
<p>Ultimately, I think there’s some potential in Aragon Court or Kleros-style dispute resolution protocols in the area of content moderation for public communities. After all, content moderation doesn’t require the intricacy of contractual law, and also content is public by default.</p>
<p>But when it comes to giving DAOs tools to create better agreements with each other or their contributors, a different set of tradeoffs was needed. We realized that a composable dispute resolution system with predictable guidelines and constraints (laws) and where participants can keep their privacy, was needed to onboard the next 10k DAOs.</p>
<h2>
<a name="enter-nation3-4" href="#enter-nation3-4"></a>Enter Nation3</h2>
<p>After creating a vibrant community of Sovereign Individuals around Nation3, we asked ourselves: what’s the most fundamental service a cloud nation can provide?</p>
<p>Eventually we realized it is a system of law, which then enables a healthy economy and market environment to exist, in turn giving birth to more products and services that citizens can benefit from. Following that logic, we <a href="https://forum.nation3.org/t/nation3-court-a-backbone-to-bootstrap-a-circular-economy-by-increasing-trust-between-citizens/553">started working on Nation3 Court <span>4</span></a>.</p>
<p>Now we are about to launch the Nation3 jurisdiction, including a <a href="https://github.com/nation3/jurisdiction">fully functioning court system <span>3</span></a>, <a href="https://linked.md/v?u=https://linked.md/api/github/nation3/law/main/Constitution.linked.md">a constitution <span>3</span></a> and <a href="https://docs.nation3.org/jurisdiction/overview">other checks and balances <span>4</span></a>.</p>
<p>Nation3 will allow anyone, for the very first time, to enter legally-binding agreements over the Internet, with no need to ultimately rely on a traditional jurisdiction.</p>
<h2>
<a name="aragon-nation3-integration-5" href="#aragon-nation3-integration-5"></a>Aragon &lt;&gt; Nation3 integration</h2>
<p>These are some of the opportunities that Nation3 can bring to Aragon:</p>
<ul>
<li>
<strong>Disputable voting</strong>: This was envisioned by Jorge and I and <a href="https://blog.aragon.org/technical-details-of-the-aragon-network/">partly implemented by the Aragon One team <span>2</span></a>. DAO token holders can deposit collateral and make a proposal to undergo a vote, but if such proposal contradicts the DAO’s charter, anyone can dispute it. This means only actions that align with the DAO’s charter and the law can pass — closing off countless attack vectors for DAOs.</li>
<li>
<strong>Disputable streams</strong>: Imagine disputable Sablier/Superfluid streams. For example, enabling DAOs to enter an agreement with each guild, and then have their ops guild being able to oversee the work of a guild and pause the stream if needed. Any of the parties can open a dispute if they feel the agreement has been breached. This is unprecedented. Right now the status quo gives almost unparalleled power to the DAO (if payments are after work is delivered) or to the recipient (if payments are upfront, before work is delivered). This obviously hurts trust, in turn hurting efficiency and stability. Nation3 provides credibly neutral streams in which every party is equal before the law, once and for all removing the cat and mouse game of payment flow.</li>
<li>
<strong>Trustless</strong> <strong>Aragon DAO</strong>: The current design of the Aragon DAO involves a trusted group of people that can veto changes over the Guardians, which are entrusted with the duty of ensuring that proposals adhere to the DAO’s charter. Unfortunately, this poses a centralization risk and a burden for the people in those positions. Using Nation3 would eliminate both. The DAO’s charter could define actions that are illegal, such as funding or undertaking any criminal activities, or paying out dividends. It would offer a higher level of legal certainty to all DAO participants.</li>
<li>
<strong>Eventual legal recognition for DAOs in SEZ</strong>: Nation3 is cloud-first, land-last. Nation3 aims to prove that it can run an Internet-native jurisdiction and a system of law first, and then negotiate the creation of Special Economic Zones in traditional jurisdictions. Traditional jurisdictions, which aren’t Web3-native, need to resort to violence and coercion to enforce legal rulings over cryptoassets. On the other hand, Nation3 is a Web3-native jurisdiction where cryptoassets and DAOs are the default, and rulings over them are enforceable on-chain.</li>
</ul>
<h1>
<a name="financials-6" href="#financials-6"></a>Financials</h1>
<p>To formalize this partnership, the following token swaps would happen:</p>
<ul>
<li>1k NATION for 300k ANT.</li>
<li>1k NATION for 1m USDC/DAI.</li>
</ul>
<p>All NATION and ANT will be subject to 1-year linear vesting.</p>
<p>For Nation3, 2k NATION represents ~5% of the total supply. For Aragon, 300k ANT represents ~0.69% of the total supply, and $1m represents ~0.5% of the treasury.</p>
<p>Aragon gets a unique chance to seed the world’s first Internet-native jurisdiction, and Nation3 gets a unique chance to achieve distribution to the world’s top DAOs.</p>
<h1>
<a name="risks-7" href="#risks-7"></a>Risks</h1>
<ul>
<li>External factors (like a regulatory crackdown taking the industry unprepared) might decrease DAO usage, slowing down the adoption of Nation3 agreeements. The Nation3 jurisdiction really flourishes with Web3-native use cases.</li>
<li>Tokens can be volatile in their value and both sides might face economic losses.</li>
<li>Smart contract bugs in aragonOS (both used by Aragon DAO and Nation3 DAO) can result in economic loses.</li>
</ul>
<h1>
<a name="proposal-execution-8" href="#proposal-execution-8"></a>Proposal execution</h1>
<ol>
<li>First of all, both DAOs need to vote on the proposal with their respective governance processes.</li>
<li>After votes pass, since this proposal requires asynchronous execution for both parties, both parties can enter a commitment agreement within the Nation3 jurisdiction (it’s great dogfooding). <a href="https://linked.md/v?u=https://linked.md/api/github/luisivan/agreements/main/TokenSwap.linked.md">Draft here <span>11</span></a>. Both DAOs can designate a committee to enter such agreement in behalf of the DAO (e.g. Budget DAO for Aragon, Meta Guild multisig for Nation3). Aragon can join with 33,333 ANT, Nation3 can join with 100 NATION. All tokens will be able to be withdrawn after the swap has been executed. It’s as easy as clicking <em>Join</em> in here: <a href="https://agreements.nation3.org/agreement/0xd9b33c228a4df2ce26f72ba42410f058f8b8851bd04e68a183dda1eef600044a">Nation3 Agreements <span>3</span></a> and here <a href="https://agreements.nation3.org/agreement/0x58c369fa3d541cdc33b991cd5d6842a96bb650738eb9f405d4f0ee375bed2f89">Nation3 Agreements <span>2</span></a>
</li>
<li>Two 1-year <a href="https://github.com/OpenZeppelin/openzeppelin-contracts/blob/master/contracts/finance/VestingWallet.sol">vesting smart contracts <span>5</span></a> will be deployed, with the start day of the vesting being the 10th of March of 2023.</li>
<li>The Aragon DAO and the Nation3 DAO will deposit 300k ANT and 2k NATION in each contract, respectively.</li>
<li>The Aragon DAO will send 1M USDC to the Nation3 DAO.</li>
</ol>

Decentralizing Aragon’s governance: Possible first steps

Thoughts on Aragon client roadmap

Next steps towards the Aragon Network DAO

Product Working Group membership thread

Financial Proposal: Aragon <> Nation3 partnership & token swap

Got something to add?