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 #200

Closed
KanoczTomas opened this issue Jan 31, 2019 · 2 comments
Closed

Batch reimbursement #200

KanoczTomas opened this issue Jan 31, 2019 · 2 comments
Labels

Comments

@KanoczTomas
Copy link
Contributor

Previous batch reimbursement: #195

@KanoczTomas
Copy link
Contributor Author

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

image

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

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

@KanoczTomas
Copy link
Contributor Author

Related transactions batch closed with:
cat support-200.csv |sed 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/200#issuecomment-478079552" {}

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

No branches or pull requests

1 participant