update branch

AGPs/AGP-10.md

@@ -35,4 +35,4 @@ Apps: Voting, Finance, and all default apps, configured so that only ANT holders
 
 The purpose of the Bounty DAO is to fund low-cost, low-risk bounties that are proposed and voted on by ANT holders. Transfers can be proposed by any ANT holder at any time, either before or after completing work. It is up to the authors of each proposal to argue the merits of their proposal and convince ANT holders to approve it. The designated venue for discussing proposals is the [Aragon community forum](https://forum.aragon.org/c/community).
 
-Since the Aragon forum is the venue for discussing Bounty DAO proposals, the contents of proposals must necessarily adhere to the [Code of Conduct](https://wiki.aragon.org/documentation/Code_of_Conduct/) governing the Aragon forum, or else risk losing their audience and potential base of support. When the author is ready to create the transfer to fund the proposal, they should put the link to the forum discussion in the reference field so there is a record of what the transfer is for.
+Since the Aragon forum is the venue for discussing Bounty DAO proposals, the contents of proposals must necessarily adhere to the [Code of Conduct](https://wiki.aragon.org/about/code_of_conduct/) governing the Aragon forum, or else risk losing their audience and potential base of support. When the author is ready to create the transfer to fund the proposal, they should put the link to the forum discussion in the reference field so there is a record of what the transfer is for.

AGPs/AGP-103.md

@@ -0,0 +1,34 @@
+---
+AGP: 103
+Title: Aragon Network Budget
+Author: anteater (@anteater0x), Luke Duncan (@lkngtn)
+Status: Approved
+Track: Meta
+Created: 2019-10-02
+---
+
+# AGP-103: Aragon Network Budget
+
+## File changed (AGP-0 or AGP-1)
+
+AGP-1
+
+## Link to proposed change
+
+https://github.com/aragon/AGPs/pull/102
+
+## Motivation for making this change
+
+I saw on the AGP wishlist that there is demand for an annual budget for the Aragon Network. I have been spending some time thinking about this ever since I took time to evaluate the financial impact of Aragon Black’s first AGP, and with spending ramping up further after the approval of Autark’s second proposal and potentially even further with Aragon Black’s second proposal, the need to put some kind of cap on spending seems more urgent than ever.
+
+I worry that ANT holders are becoming short-sighted about how they are managing the treasury, and I hope a budget will impose some discipline on spending while the Aragon Network is still running at a loss. We cannot continue saying “yes” to every good looking proposal. A budget provides us a common agreement we can point at to justify why certain good proposals can be funded and others cannot.
+
+I propose that we, the Aragon community and ANT holders, make a “Ulysses pact” with ourselves to not spend more than 5% of our treasury’s value, or 250,000 DAI, whichever is greater, in any given Aragon Network vote cycle. The result is that we will always have five or more years worth of runway, until we get down to a treasury value of 5 million DAI and spending is capped at 250,000 DAI per vote cycle.
+
+**References**
+- https://forum.aragon.org/t/agp-wishlist-and-blacklist/355
+- https://forum.aragon.org/t/aragon-flock-proposal-aragon-black/646/8
+- https://en.wikipedia.org/wiki/Ulysses_pact
+
+## License
+Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/).

AGPs/AGP-104.md

@@ -0,0 +1,65 @@
+---
+AGP: 104
+Title: Aragon App Mining
+Author: lkngtn (@lkngtn)
+Status: Approved
+Track: Finance
+Created: 2019-10-02
+---
+
+# AGP-104: Aragon App Mining
+
+## Address of the transfer recipient
+
+0xe0d11d5a1982f64ff1d36cd8c2bd315dea127d66 (Agent of pinion.aragonid.eth)
+
+## Amount of the transfer
+
+100,000 ANT
+50,000 DAI
+
+## Number and frequency of transfers if recurring (enter “1” if only one payment will be made)
+
+Quarterly transfers of 100K ANT with no expiration date, beginning after ANV-5 and due the week after each ANV.
+One-time transfer of 50K DAI for initial execution and launch of the App Mining program.
+
+## Purpose of the transfer
+
+To fund an "Aragon App Mining" program that rewards developers for creating and maintaining Aragon applications. The policy is inspired by [Blockstack's App Mining program](https://app.co/mining).
+
+A core value proposition of Aragon is that it is a platform that allows users to pull from a library of modular and composable applications to create and operate an organization on-chain. In order to attract application developers to the platform we need to provide a stable opportunity that encourages entrepreneurial developers to understand user needs, develop applications, ship them to mainnet, and to continue to maintain and improve them over time.
+
+At the moment there is no incentive to do this outside of one-off grants. There has been discussion to create monetization models for the eventual release of the App Center, but currently such a system doesn't yet exist, and even if it did the number of users of Aragon is small enough that such a market may not be attractive enough to bring top talent into the space. Users will come if there are high quality apps, but if there are no users, no high quality apps will be built and maintained.
+
+To remedy this I propose we bootstrap the supply side by allocating funds and distributing them to Aragon application developers based on agreed upon KPIs. We can combine multiple KPIs into an **Aragon App Score**, which we can use to rank applications and then use the ranking to distribute funding to maintainers on a periodic basic.
+
+**The following weighted KPIs are not final and intended for illustration purposes:**
+
+| KPI | Formula | Weight |
+| -------- | -------- | -------- |
+| Utility    | Sum of (# of transactions involving an application ) | 30%  |
+| Value-weighted utility    | Sum of (# of transactions involving an application * DAI value of organization's treasury) | 30%    |
+| Popularity    | Sum of (# of installations) | 10%  |
+| Value-weighted popularity    | Sum of (# of installations *  DAI value of organization's treasury) | 30% |
+
+To compute the DAI value of an organizations treasury we would use the *default vault* and compute the DAI value of ETH, ANT, and DAI held by the organization.
+
+To compute the # of transactions involving an application we would simply examine the blockchain.   
+
+For each payout cycle, there is a determined “pot” of total earnings that will get paid to apps. The top app gets paid 20% of the total pot. So, for a pot of 100K ANT, the top app receives 20K ANT. The next app gets paid 20% of the remaining pot. The remaining pot is 80K, and 20% of that is 16K ANT. This process continues until either every app has been paid or the payout amount is below 200 ANT, whichever comes first.
+
+**Blacklist**
+
+It's possible that the KPI mechanism can be gamed, for example the popularity metric could be manipulated by creating a bunch of organizations and installing a bunch of otherwise unpopular applications. For the purposes of our initial pilot, rather than try to engineer an un-gameable metric, we propose that we can rely on the community to report potential abuse and the discretion of Pinion to manage a blacklist for the purpose of excluding recipients that are suspected to be trying to maliciously manipulate payout amounts. In the future, this role could be decentralized by leveraging the Aragon Court.
+
+**Initial and Ongoing Execution**
+
+This proposal includes a one-time 50K DAI budget for Pinion to execute on the development and documentation effort related to surfacing these metrics to the community and preparing the initial launch of the App Mining program.
+
+If approved, Pinion would:  
+
+- Work with the community to determine KPIs and process for determining the Aragon App Score so that it can be implemented before the next ANV. The initial app mining payout is scheduled to begin after ANV-5 giving the community a chance to adjust the budget and confirm the Aragon App Score if the community desires.  
+- Work with [Apiary](apiary.1hive.org) to create a dashboard that includes these metrics and make the Aragon App Score publicly and easily accessible to the Aragon community.  
+- Provide documentation via PRs to hack.aragon.org for application developers to participate in the program.  
+- Assist the Aragon Association ("AA") and/or teams responsible for Aragon communications in preparing communications for the launch of Aragon's App Mining program.  
+- Coordinate with the AA to execute payments each quarter to eligible recipients based on calculated Aragon App Scores.

AGPs/AGP-105.md

@@ -0,0 +1,28 @@
+---
+AGP: 105
+Title: Allow Finance proposals that could otherwise fit in Nest or Flock
+Author: lkngtn (@lkngtn)
+Status: Approved
+Track: Association
+Created: 2019-10-02
+---
+
+# AGP-105: Allow Finance proposals that could otherwise fit in Nest or Flock
+
+## Description of desired Association policy change
+
+During ANV-3, AGP-72 was rejected by the Aragon Association ("the Association", or simply "the AA") with the following reasoning:
+
+> Historically, the Aragon Association board has been rejecting Finance Track AGPs that could fit in the Nest or Flock grant programs instead. The Nest and Flock programs are the only two ways the Aragon Association currently manages grants programs, and to fund something outside of them, when they could fit there, would create a bad precedent. Should there be a need for a different funding mechanism for specific projects, an AGP should be created to set the guidelines, budget and governance for such a program.
+
+Source: https://forum.aragon.org/t/agp-reviews-for-anv-3-by-the-aragon-associations-board/1117
+
+This proposal is to change the Association policy on rejecting these types of proposals on this basis. It would still allow the Association to use its discretion on approving or rejecting proposals, but proposals should not be rejected on the basis that they would otherwise fit into a different program that is outside of the AGP process.
+
+## Motivation for changing this Association policy
+
+Both Flock and Nest are useful programs, and it may be reasonable to divert Finance proposals that would be a good fit for those programs away from the AGP process. However, doing so significantly reduces the flexibility and power of Finance track AGPs. This proposal gives ANT holders an opportunity to weigh in on this policy change. Rejecting this proposal would indicate that ANT holders would like the AA to continue to reject proposals if they would otherwise fit into Flock, Nest, or a similar program, and approving this proposal would require the AA to change this policy of rejecting on the basis that a proposal could potentially go through Flock, Nest, or a similar program.
+
+
+## License
+Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/).

AGPs/AGP-106.md

@@ -0,0 +1,64 @@
+---
+AGP: 106
+Title: Develop and launch Aragon Chain
+Author: Aidan Hyman & Gregory Markou
+Status: Approved
+Track: Finance
+Created: 2019-10-03
+---
+
+# AGP-106: Develop and launch Aragon Chain
+
+## Address of the transfer recipient
+
+0xfc6eBB0F689674b18f90dA73658072155e98ea5B
+
+## Amount of the transfer
+
+A total of $500,000 USD will be allocated to the Aragon Chain. Invoices will be sent to the Aragon Association, and compensation will be at their discretion.
+
+## Number and frequency of transfers if recurring (enter “1” if only one payment will be made)
+
+1
+
+## Purpose of the transfer
+
+At the moment, Aragon fully depends on Ethereum mainnet in order to function.
+
+However, Ethereum may not be the best platform for all Aragon use cases. Some Aragon organizations may not want to pay the security and composability premium for being on Ethereum.
+
+On top of this, we are seeing increased development and user experience costs [resulting from changes in the Ethereum protocol that break Aragon organizations](https://www.coindesk.com/ethereums-istanbul-upgrade-will-break-680-smart-contracts-on-aragon).
+
+Building a sovereign layer 1 protocol owned and operated by the Aragon community will ensure that we can continue enhancing Aragon, and even introduce protocol changes that make running decentralized organizations easier and cheaper. This way we can offer Aragon organizations another option parallel to Ethereum, with different security, cost, and performance trade-offs. The idea is for this chain to be heavily focused and optimized for the Aragon use case, so other heavyweight use cases that are currently clogging the Ethereum network wouldn't necessarily have any incentives to run on the Aragon Chain.
+
+The Aragon Chain will be an EVM-compatible Proof of Stake blockchain whose native staking token is derived from ANT (in a similar fashion as the Aragon Court's ANJ).
+
+Aragon One has worked with ChainSafe Systems on a feasibility study on what the most fitting technology for building the Aragon Chain is. We are now certain of the way forward and it's ready to get into the specification and development phase.
+
+Feasibility report: [PDF](https://github.com/ChainSafe/AGP-Report/blob/master/Aragon%20Feasability%20Report%20-%20Oct%209%2C%202019.pdf)
+
+The report goes in-depth between the current leading staking chains: Polkadot and Cosmos. Throughout the report comparisons are made based on Aragon-specific optimizations, and cross-chain communication.
+
+Deliverables from this project:
+
+- Publish Aragon Chain spec  
+- Develop full-node software that follows the Aragon Chain spec  
+- Launch Aragon Chain testnet  
+- Launch Aragon Chain mainnet  
+
+## Recipient information
+
+Organization (if any)  
+Name: ChainSafe Systems  
+Website: www.chainsafe.io  
+Other URL: www.github.com/ChainSafe  
+
+Fill out the following information for each individual team member who will be managing funds from this transfer:
+
+Name: Gregory Markou  
+PGP key fingerprint: 00BA 1344 6C1B 51D8 C730  131B EE32 8DC9 AD61 010C  
+Website: www.chainsafe.io  
+Other URL: www.github.com/GregTheGreek  
+
+## License
+Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/).

AGPs/AGP-112.md

@@ -0,0 +1,31 @@
+---
+AGP: 112
+Title: Oppose any change to Ethereum's mining algorithm before Ethereum 2.0
+Author: anteater (@anteater0x)
+Status: Approved
+Track: Proclamation
+Created: 2019-09-22
+---
+
+# AGP-112: Oppose any change to Ethereum's mining algorithm before Ethereum 2.0
+
+## Proclamation text
+
+ANT holders who vote "yes" on this proposal oppose Ethereum changing its proof-of-work mining algorithm before the switch to proof-of-stake as part of the Ethereum 2.0 roll-out, unless such change is intended as an "emergency fix" to a fatal flaw in the current mining algorithm. A "fatal flaw" is defined here as a flaw that breaks the expected functionality of Ethereum (e.g. if blocks are consistently mined too quickly or too slowly, or if blocks could be mined by some miners faster than others despite having equal hashpower) or causes Ethereum to completely stop working (i.e. stop producing blocks and confirming valid transactions).
+
+This AGP includes opposition to the "[tenatively accepted](https://github.com/ethereum/EIPs/blob/master/EIPS/eip-1679.md#tentatively-accepted-eips)" [EIP-1057: ProgPoW, a Programmatic Proof-of-Work](https://eips.ethereum.org/EIPS/eip-1057), and any other proposed changes to Ethereum's proof-of-work mining algorithm that don't fit reasonable criteria of an "emergency fix" as described above.
+
+## Motivation for writing this proclamation
+
+Ethereum is currently working as expected, and so the proposal author sees no reason to change the mining algorithm now or at any time in the foreseeable future before the switch to Ethereum 2.0 proof-of-stake.
+
+Other opposition to changing Ethereum proof-of-work:
+- https://twitter.com/koeppelmann/status/1109229299331145730
+- https://twitter.com/BobSummerwill/status/1174110277328990209
+
+ProgPoW debate points:
+- https://trello.com/b/KrD25QI5/progpow
+- https://www.kialo.com/ethereum-and-programmatic-proof-of-work-progpow-30878
+
+## License
+Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/).