You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 8, 2018. It is now read-only.
Gittip's escrow is stored across multiple accounts (Balanced, New Alliance, PayPal, cold storage etc.; see #1988, whence this is reticketed). We see spikes in withdrawals when someone accumulates money in Gittip over a year and then connects a funding sink. It takes time to move money between those accounts, so, while we always have everyone's full escrowed amount available within our escrow as a whole, we do run the risk of not having someone's money available right now for a particular sink type.
To mitigate this risk, we should cap withdrawals. The algorithm should be something like:
Reduce the amount of the top withdrawer in a batch as needed, down to the amount of the second-highest withdrawer.
If that's not enough, reduce the amount of the first- and second-highest withdrawers down to the amount of the third-highest. Etc.
We should do this similarly for both Balanced and PayPal.
We should mention this in the note for the exchange.
We should ensure that this interacts with escrow rebalancing (#1092) in such a way that users are only affected by this cap for a week or so.
Gittip's escrow is stored across multiple accounts (Balanced, New Alliance, PayPal, cold storage etc.; see #1988, whence this is reticketed). We see spikes in withdrawals when someone accumulates money in Gittip over a year and then connects a funding sink. It takes time to move money between those accounts, so, while we always have everyone's full escrowed amount available within our escrow as a whole, we do run the risk of not having someone's money available right now for a particular sink type.
To mitigate this risk, we should cap withdrawals. The algorithm should be something like:
We should do this similarly for both Balanced and PayPal.
We should mention this in the note for the exchange.
We should ensure that this interacts with escrow rebalancing (#1092) in such a way that users are only affected by this cap for a week or so.
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: