-
Notifications
You must be signed in to change notification settings - Fork 12
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 #1663
Comments
The batch transaction with txid has been broadcast and should be included in blocks soon. The following process could not be carried out due to some incorrect payouts in the past. 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:
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 there are 24 outputs for this reimbursement transaction. I assume one is the change address. Therefore, 23 reimbursement issues were paid out. On the report only 4 issues are linked. Are there more issues paid out other than those listed? I also think it would be good to reference the total amount of bitcoin reimbursed in these reports otherwise one has to guess which is the change address, or use a process of elimination if all issues are correctly referenced. |
Thank you for the comment @pazza83 , here is the response:
Correct
Correct, I think it was actually 20 issues because one of them contained several reimbursements within one.
Yes, the report was incomplete and I have just added the rest.
Yes, will add the specific amounts of btc on the role report. Let me know if there is anything else best, |
No, that one was on the "waiting for info" column and I missed it. Just moved it to "ready" for next cycle. Thank you. |
Previous batch reimbursement #1623
The text was updated successfully, but these errors were encountered: