Skip to content
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

Batch Reimbursement #481

Closed
leo816 opened this issue Aug 12, 2020 · 2 comments
Closed

Batch Reimbursement #481

leo816 opened this issue Aug 12, 2020 · 2 comments
Assignees

Comments

@leo816
Copy link
Contributor

leo816 commented Aug 12, 2020

Previous batch reimbursement: #430

@leo816 leo816 self-assigned this Aug 12, 2020
@leo816 leo816 added this to Todo in Lost fee reimbursements via automation Aug 12, 2020
@leo816
Copy link
Contributor Author

leo816 commented Sep 25, 2020

The batch transaction with txid
598753ba993a31ccf6a7c260b889965d5f96407aea4c837756a396d8bb57027a has been broadcast and should be included in blocks in a few days.

Screen Shot 2020-09-26 at 00 12 49

The transaction was created against support-481.csv file at the root of this repo at commit b5414de. The csv file for creating electrum transaction was created with the following command:

$ gawk -F, '{ addresses[$3] += $4+$5 } END { for (address in addresses) printf "%s,%f\n", address, addresses[address]}' support-481.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.

@leo816
Copy link
Contributor Author

leo816 commented Sep 25, 2020

Related issues were closed with:

cat support-481.csv |gsed 1d|cut -d, -f1|uniq|xargs -I {} ghi close -m "Closing as reimbursed via the batch transaction documented at https://github.com/bisq-network/support/issues/481#issuecomment-699182913" {}

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

No branches or pull requests

1 participant