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

cap withdrawals #2096

Closed
chadwhitacre opened this issue Feb 28, 2014 · 1 comment
Closed

cap withdrawals #2096

chadwhitacre opened this issue Feb 28, 2014 · 1 comment

Comments

@chadwhitacre
Copy link
Contributor

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.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

@chadwhitacre
Copy link
Contributor Author

Closing in light of our decision to shut down Gratipay.

Thank you all for a great run, and I'm sorry it didn't work out! 😞 💃

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

No branches or pull requests

2 participants