[bisq-network/support] Batch Reimbursement (#576)

[leo816]

The batch transaction with txid
[33efe6e3b9c08d70cf803a203d6995ab3aa465c4d8a138ac3a58faff2c989584](https://blockstream.info/tx/33efe6e3b9c08d70cf803a203d6995ab3aa465c4d8a138ac3a58faff2c989584) has been broadcast and should be included in blocks in a few days.


<img width="1088" alt="Screen Shot 2020-12-22 at 12 00 13" src="https://user-images.githubusercontent.com/54798241/102881619-6b66c580-444d-11eb-915e-5fc0d420969d.png">


(The transaction was created against support-576.csv file at the root of this repo at commit b5414de. The csv file for creating electrum transaction was created with the following command:) *The standard process failed and I had to do the payout manually since the information registered after I processed the information was innacurate such as the btc addresses and as I informed the previous role holder and other devs, the same commands weren't working like before. I have been waiting for some answers but since a cycle has passed by, we can't let users keep waiting to receive their funds back.

`$ gawk -F, '{ addresses[$3] += $4+$5 } END { for (address in addresses) printf "%s,%f\n", address, addresses[address]}' support-515.csv |grep -v address > reimbursement.csv`

This prints out addresses to reimburse (column 3) and sums up the trading and mining fee per address (column 4 and 5). As there are payouts to the same address the script sums them up so there is only one line in the csv file, reducing the resulting transaction size and fee. The command also eliminates the header line.

The resulting csv file was fed to Electrum in the Send screen using the Tools -> Pay to many menu option.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/support/issues/576#issuecomment-749487833
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20201222/1e54154a/attachment.htm>