-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Refund agent to partially reimburse high volume trades #296
Comments
Is there a GitHub issue you can point me to that where the 0.5 BTC limit was introduced? |
I think the 0.5 BTC limit is just what @RefundAgent chose to limit direct refunds to after taking too much risk with a larger refund. The refunds done by refund agents are out of pocket and a personal risk they take so it's really up to them how much to refund. The initial discussion, before the 2of2 protocol, around refunds by agents vs going to the DAO included thoughts of the refund agents (or anyone, not as a dedicated role) buying the claims at a discount for traders to get their refund as soon as possible and then having the refund agents claiming these cases to the DAO. I think the BSQ market is still not liquid enough for that to work, and users seem to get upset when they miss out on the counterparty's deposit. |
Hi @refund-agent2 I am doing some housekeeping on the proposals. Please can you take steps to move this forward or alternatively close the proposal. Many thanks. |
Hi @refund-agent2 just following this up. Please can you move this proposal forward or close it. Also I was under the impression that partial reimbursements have started is this the case? |
Hi @refund-agent2 just following this up. Are you currently partially reimbursing traders? |
Yes, I think it was only needed once, for trade NVLSXv in Cycle 24. |
Closing as approved as this is now in practice and there have been no views to the contrary |
Trader asks for this at trade reimbursement case:
I agree with it, but with some considerations:
Pros:
Cons:
The text was updated successfully, but these errors were encountered: