Skip to content
This repository has been archived by the owner on Feb 8, 2018. It is now read-only.

compute 1.0 balances #3747

Closed
wants to merge 5 commits into from
Closed

compute 1.0 balances #3747

wants to merge 5 commits into from

Conversation

chadwhitacre
Copy link
Contributor

Needed for #3744.

@chadwhitacre chadwhitacre added this to the Balanced Shutdown milestone Sep 2, 2015
@chadwhitacre
Copy link
Contributor Author

I want to write one SQL script that computes all 1.0 balances, and then run it.

@chadwhitacre
Copy link
Contributor Author

We need to compute 1.0 balance as a function of current balance. Actually, "1.0 balance" is really "remaining 1.0 balance," i.e., the amount received under 1.0 that is still in our escrow.

@chadwhitacre
Copy link
Contributor Author

My hunch is that the function could be some summation of transfers and payments and exchanges since 2015-05-07.

The next step is to compute *remaining* 1.0 balance.
 - exclude failed exchanges
 - throw away participants with zero balance at Gratipocalypse
@chadwhitacre
Copy link
Contributor Author

Your remaining 1.0 balance is your balance at the Gratipocalypse, minus anything you gave away (transfers and payments) or withdrew (exchanges) since then. The payins and receipts since the Gratipocalypse are irrelevant.

@chadwhitacre
Copy link
Contributor Author

Counting that way, we are at 2,173 participants and a total of $130,112.10.

@chadwhitacre
Copy link
Contributor Author

Alright, so ... ideally we would have not had any 1.0 leaks, and we would be paying out in full every week under Gratipay 2.0, so that it was guaranteed that for anyone with a balance, their balance was their Gratipay 1.0 balance.

However, we a) leaked 1.0 money, and b) haven't paid out everyone every week under Gratipay 2.0. What are the details with those cases?

@chadwhitacre
Copy link
Contributor Author

We leaked 1.0 money in three ways:

@chadwhitacre
Copy link
Contributor Author

The tiny bit we transferred from two participants to a third as part of a take-over is fine, because it's the same person, and so they'll have to apply for a payout in order to get the money anyway.

The amount we leaked as final gifts is effectively still 1.0 money, it's just that the participants that received it will have to apply for a payout to extract it instead of the participants who were holding that money on the day of the Gratipocalypse.

It's like hot potato. :-) 🔥 🚰

The paid-out money, we recovered. So that's fine.

@chadwhitacre
Copy link
Contributor Author

The fourth way we leaked 1.0 money was with 2.0-style payments, and this is the most significant way. Of the 2,259 participants who received money under Gratipay 1.0, 215 (9.5%) have made voluntary payments under Gratipay 2.0. These payments decremented their Gratipay 1.0 balance.

@chadwhitacre
Copy link
Contributor Author

My next step here is to frame the above in terms of the columns in the numbers_1_0 table.

@chadwhitacre
Copy link
Contributor Author

These payments decremented their Gratipay 1.0 balance.

And, more importantly, that money left the system, because the recipients were cleared for payouts.

@chadwhitacre
Copy link
Contributor Author

Reticketed immediately refunding failed payouts as #3754. We want it to be the case that the only money in escrow is 1.0 money, or 2.0 money that is below the payout threshold.

@chadwhitacre
Copy link
Contributor Author

Only 103 out of 2,209 (4.7%) have a current balance that is not equal to their remaining 1.0 balance. Only 241 (10.9%) have a balance that has moved at all since the Gratipocalypse. I think for the purposes of the 1.0-payout page (#3744) we can treat current balance as the 1.0 balance. Most people with a balance under $10 aren't going to apply for a payout, and/or are going to know that they're giving. We should refund the charged-in-advance money, though.

@chadwhitacre chadwhitacre deleted the 1.0-balances branch September 4, 2015 02:14
@chadwhitacre
Copy link
Contributor Author

I ended up merging this branch into #3744 as 1cc6065.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant