[bisq-network/proposals] Have a clearly defined process for how Burning man trades BTC from donation and trade fee addresses for BSQ (Issue #367)

[pazza]

> The main changes with this proposal should be to have a clear schedule when funds in the donation address can be spent by burning man. More clarity is needed. How long do users have to start requesting a reimbursement?

I agree, I opened another issue at the same time as this one: 
[Have a clearly defined process for how users with accepted DAO reimbursement requests can trade with Burning Man](https://github.com/bisq-network/proposals/issues/366) 

It would be great to have your input on this proposal also :)

> What if the discussions around the reimbursement takes too long to get accepted in the next cycle but are then accepted in the one after?

I think I proposed reimbursed users should have 1 cycle to trade with yourself following their reimbursement request being accepted. After that there would be no special privileges for them to trade directly with yourself.

 > I don't think there will be a big change in BSQ bought on market as a result of this. There is one big output that has not been claimed by a user which is the reason there is more than the usual amount of BTC in the donation address. That is the reason for this proposal I believe. I doubt there will be many such cases.

There is [3.39 BTC](https://mempool.space/address/34VLFgtFKAtwTdZ5rengTT2g2zC99sWQLC) in the donation address now. Which user/s are waiting to trade with you?

I agree that there will not be a change in BSQ bought, just think it will give more clarity around when and how BSQ is bought by Burning Man.

> I suggest making the announce of burning man trading not strict but recommended.

@ghubstan what are your thoughts on announcements being recommended but not strict?

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

Message ID: <bisq-network/proposals/issues/367/1073122902 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20220319/0d8f6948/attachment.htm>