[bisq-network/proposals] Have a clearly defined process for how users with accepted DAO reimbursement requests can trade with Burningman (Issue #366)

[refund-agent2]

This issues were already discussed when I began with this role. I launched two proposals: [limit to 0.5BTC](https://github.com/bisq-network/proposals/issues/296) the reimbursements for each trade and [define prices for reimbursement](https://github.com/bisq-network/proposals/issues/294). They were approved without much discussion, but the conclusions weren't submitted to the Wiki.
I agree with the need to clarify and point to the wiki this process.

Traders have known they have the right to sell their BSQ to burningman since I always tell them as soon as I realize the amount is big. I find one whole cycle too much for trading with burningman, next one or two Sundays should be enough for trading in order to reach a smooth process and reduce option trading risk.

I have been [reporting](https://github.com/bisq-network/roles/issues/93#issuecomment-997368810) when traders are going to need a refund, but only sometimes I have been reported back that the trades have been really performed. As after each cycle I also get a reimbursement and need to trade with burningman, I think it's ok if I'm the one linking traders and burningman for this trades; i.e. sending a message to burningman with the offers to pick after traders announce me they're willing to sell their BSQ. 
Currently traders were talking directly to burningman.

As I stated in #294 I don't find that promising a fixed rate is the best deal, since any other DAO participants have to deal with volatility. I think it's much better to use 30 day average at the moment of requesting the reimbursement and  the 30 day average at the time of trading with burningman. Anyways, whatever it is decided, I think I should have the same deal as traders. Reimbursements are the same, the only difference is that I get a compensation and do it more often.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/proposals/issues/366#issuecomment-1057962515
You are receiving this because you are subscribed to this thread.

Message ID: <bisq-network/proposals/issues/366/1057962515 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20220303/7424a287/attachment.htm>