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

After lightning wallet transactions between internal LndHub accounts finished, corresponding lightning invoices did not get closed #461

Open
zwan2016 opened this issue Jun 23, 2022 · 2 comments

Comments

@zwan2016
Copy link

zwan2016 commented Jun 23, 2022

LndHub version: v1.4.1
Lnd version: v0.14.3-beta
BlueWallet version: 6.2.12 (build 1643409602 master)

We are only discussing Lightning Wallets on BlueWallet app, and the Lnd node is running in testnet mode.

Issue:
There are 2 BlueWallet Lighting wallets loaded with some satoshi, 'wallet A' generates an invoice using BlueWallet, 'wallet B' then pays this invoice through BlueWallet, and 'wallet A' received the money as expected, this money got deducted from 'wallet B' balance as well. This is all inside of one instance of LndHub, so there is no need to go through lightning network, and it doesn't. Everything is expected except the generated lightning invoice is not closed, it still can be paid through lightning network. And if you paid it anyway, this payment won't reflect on 'wallet A' balance.

In my imagination, once this internal transaction finished, the generated lightning invoice should be closed in lightning network. Please confirm this issue, or maybe this is a designed behavior and I missed something.

@Overtorment
Copy link
Member

this is expected.

PS. i dont see a way to 'close' unpaid invoice. even it there were, that would require to add more code in handling lndhub's internal invoices to fix very obscure use case that never happens

@zwan2016
Copy link
Author

Hi @Overtorment , I believe this api (https://api.lightning.community/#cancelinvoice) would be able to cancel an unsettled invoice.

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

2 participants