Skip to content
This repository has been archived by the owner on Jul 18, 2020. It is now read-only.

AGP-104: Aragon App Mining #104

Merged
merged 18 commits into from
Oct 18, 2019
Merged

AGP-104: Aragon App Mining #104

merged 18 commits into from
Oct 18, 2019

Conversation

lkngtn
Copy link
Contributor

@lkngtn lkngtn commented Oct 3, 2019

No description provided.

AGPs/AGP-LD1.md Outdated Show resolved Hide resolved
AGPs/AGP-LD1.md Outdated Show resolved Hide resolved
AGPs/AGP-LD1.md Outdated Show resolved Hide resolved
AGPs/AGP-LD1.md Outdated Show resolved Hide resolved
AGPs/AGP-LD1.md Outdated Show resolved Hide resolved
AGPs/AGP-LD1.md Outdated Show resolved Hide resolved
AGPs/AGP-LD1.md Outdated Show resolved Hide resolved
AGPs/AGP-LD1.md Outdated Show resolved Hide resolved
AGPs/AGP-LD1.md Outdated Show resolved Hide resolved
AGPs/AGP-LD1.md Outdated Show resolved Hide resolved
AGPs/AGP-LD1.md Outdated Show resolved Hide resolved
AGPs/AGP-LD1.md Outdated Show resolved Hide resolved
AGPs/AGP-LD1.md Outdated

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 every app has been paid or the payout amount is bellow 200 ANT whichever comes first.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's imagine there are five apps, pot is 100k ANT as mentioned.

#1. 20k ANT
#2. 16k ANT
#3 12800 ANT
#4 10240 ANT
#5 8192 ANT

Would the balance (32768 ANT) get sent back to the AA multisig? In any case, you should mention what happens to the leftover balance of the pot.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

bump

AGPs/AGP-LD1.md Outdated Show resolved Hide resolved
AGPs/AGP-LD1.md Outdated Show resolved Hide resolved
AGPs/AGP-LD1.md Outdated Show resolved Hide resolved
AGPs/AGP-LD1.md Outdated Show resolved Hide resolved
@john-light
Copy link
Contributor

The time now is after the published deadline of October 10, 2019 at 16:00 UTC for finalizing proposals and moving them to Stage V, and this proposal has not yet been finalized. Per AGP-1, this proposal is considered to be withdrawn and this pull request will now be closed:

If you do not finalize the proposal and request to move the proposal to Stage V before Stage V is scheduled to begin, AGP Editors will consider the proposal withdrawn and close the pull request when Stage V begins.

@john-light
Copy link
Contributor

john-light commented Oct 15, 2019

The Aragon Association Board of Directors has voted to push back the ANV-4 schedule by one week. This PR is being re-opened and is included in the Community Review Period which will now last until October 17, 2019 at 16:00 UTC. Please finalize the draft and leave a comment saying "This draft is final and ready to move to Stage V" before the end of the Community Review Period if you would like this proposal to be reviewed by the Aragon Association in Stage V.

Ref: https://forum.aragon.org/t/anv-4-delay-announcement/1367

lkngtn and others added 5 commits October 16, 2019 10:17
Co-Authored-By: Jorge Izquierdo <izqui97@gmail.com>
Co-Authored-By: John Light <john-light@users.noreply.github.com>
Co-Authored-By: John Light <john-light@users.noreply.github.com>
Co-Authored-By: John Light <john-light@users.noreply.github.com>
Co-Authored-By: John Light <john-light@users.noreply.github.com>
lkngtn and others added 10 commits October 16, 2019 10:18
Co-Authored-By: John Light <john-light@users.noreply.github.com>
Co-Authored-By: John Light <john-light@users.noreply.github.com>
Co-Authored-By: John Light <john-light@users.noreply.github.com>
Co-Authored-By: John Light <john-light@users.noreply.github.com>
Co-Authored-By: John Light <john-light@users.noreply.github.com>
Co-Authored-By: John Light <john-light@users.noreply.github.com>
Co-Authored-By: John Light <john-light@users.noreply.github.com>
Co-Authored-By: John Light <john-light@users.noreply.github.com>
Co-Authored-By: John Light <john-light@users.noreply.github.com>
@lkngtn
Copy link
Contributor Author

lkngtn commented Oct 16, 2019

This draft is final and ready to move to Stage V

Copy link
Contributor

@john-light john-light left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some open questions not yet resolved on this PR.

@lkngtn
Copy link
Contributor Author

lkngtn commented Oct 17, 2019

This is still final. I do not see any open questions that warrant a resolution/change at this time.

@john-light
Copy link
Contributor

I find this proposal to be under-specified because:

  • It does not specify what happens to the balance leftover in the "pot" after apps have been paid out.

  • It does not define what the "default vault" is in an organization that has multiple vaults installed and used.

As an AGP Editor I will forward this proposal to the Association for review in Stage V.

As a participant in the AGP process I advocate that this proposal be rejected for remaining under-specified. This ambiguity could lead to disputes later that could easily be prevented if the author put in the effort to fill in these blanks.

@lkngtn
Copy link
Contributor Author

lkngtn commented Oct 17, 2019

Noted. I will add though that the timing and cyclical nature of the ANVs does not allow for the type of specification necessary to reach broad consensus on the specific detail without it feeling rushed. In order to move forward in a timely fashion but with the flexibility to ensure there is time to reach broad consensus on the specific details I opted to structure the proposal so there are open questions that can be resolved during implementation. The first distribution does not occur until after the next ANV so if there is contention on any details of decided during the course of implementation they can be resolved through that process. But by approving now we can move forward with the resources to ensure that an app mining process can be initiated next quarter.

john-light
john-light previously approved these changes Oct 17, 2019
@john-light john-light changed the title Create AGP-LD1: Aragon App Mining AGP-104: Aragon App Mining Oct 17, 2019
@luisivan luisivan merged commit 425d1cb into aragon:master Oct 18, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants