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

Closed
leo816 opened this issue Jan 2, 2021 · 1 comment
Closed

Batch Reimbursement #703

leo816 opened this issue Jan 2, 2021 · 1 comment

Comments

@leo816
Copy link
Contributor

leo816 commented Jan 2, 2021

Previous Batch Reimbursement: #576

@leo816
Copy link
Contributor Author

leo816 commented Jan 2, 2021

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

Screen Shot 2021-01-02 at 18 36 44

The following process could not be carried out due to some incorrect payouts in the past and the payout was made manually by introducing each bitcoin address provided by each user and introducing the corresponding amount of fees:

The transaction was created against support-703.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-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.

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

No branches or pull requests

1 participant