-
-
Notifications
You must be signed in to change notification settings - Fork 127
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
Add column with transaction fees (Funding > Transactions > Export CSV) [0.5 XMR] #1254
Comments
There is a bounty on this issue, the amount is in the title. The reward will be awarded to the first person or group of people who resolves this issue. If you are starting to work on this bounty, please write a comment, so that we can assign the issue to you. We expect contributors to provide a PR in a reasonable time frame or, in case of an extensive work, updates on their progresses. We will unassign the issue if we feel the assignee is not responsive or has abandoned the task. Read the full conditions and details of our bounty system. |
I'll start looking into this one |
Is it OK to assume transaction fee = tx.getFee() in TransactionsListItem? |
Oops, sorry. I put in a PR. |
This issue is resolved with #1288 With this change, the total amounts in Funds > Transactions adds up to the total balance correctly. I'll be awarding the bounty to @niyid because his submission was first and functional, while preland's submission has an error when run (and some unnecessary formatting changes :P). While neither submission was fully correct, niyid's submission was easily adapted to display the fee for outgoing transactions. Thanks very much for your help. @niyid please message me an address for payment. Thanks! |
This issue requests adding a column for transaction fees in the generated transaction report CSV.
To generate the transaction report, go to Funding > Transactions > Export CSV.
The report only has a column for the amount of XMR transacted.
The tx fee should also appear as a column in the Funds > Transactions tab.
The text was updated successfully, but these errors were encountered: