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
Enable export of Lightning Network transactions history #8521
Comments
At the moment you can use the command line to export lightning transactions: This is just a workaround. I agree that lightning history should be exportable from the GUI. |
Note: it would also be good to merge Some operations (channel opening, channel closing, submarine swaps) affect both onchain and lightning balances, but they are not treated homogeneously: while a channel opening is seen as a single transaction, a submarine swap is represented as a compound of two transactions. We should probably represent submarine swaps a single operation first (and make the expandable item go away). Once this is done, we can have a single export history command in the CLI, and expose it in the GUI. |
@ecdsa Thank you for the reply. I entered |
sorry, my bad: |
@ecdsa I ran the command but got the error |
@ecdsa I have the same question. How to do this using the pre-compiled binaries? (e.g. using the .exe file in windows?) |
Ok Windows didn't work even with python (was getting the secp256k1 library import error even though I had in installed with pip), so I had to move to ubuntu. |
Currently, a user may export the transaction history from the 'History' tab by clicking the tool button and clicking 'Export' (screenshot below). This is helpful for accounting. However, this export does not include details of Lightning Network transactions. Exporting LN txs is needed to account for those transactions while a channel is open. Could you make an option to export the Lightning Network transactions? This would support accurate accounting and crypto tax recording. Thank you for the consideration.
The text was updated successfully, but these errors were encountered: