Background
I am currently running a Lightning Network node using the Voltage service. Due to an invalid transaction of 147 sats, most of my on-chain funds are stuck in Pending state.
A brief history of the issue:
- In the past, the channel opening transaction fee was set too low, resulting in the channel not opening properly. I then force-closed the channel.
- The funds tied to the force-closed channel returned to my on-chain wallet.
- I thought everything was going smoothly until an invalid transaction of 147 sats propagated and caused the on-chain funds to be stuck in Pending state.
- To my knowledge, this transaction started to occur after upgrading the node to version 0.16.x.
- The invalid transaction's txid is e7ace4fae0e4b732135d358a638aea1f738d8bd86d5fec07068a6d40dc4606b6, but it cannot be verified in the mempool as it is invalid.
- The reason for considering the transaction invalid is that the output address is different from the one where I received the funds after closing the channel.
- With the help of a Voltage engineer, I performed wallet rescans three times, but the issue persists.
- it seems that the problematic transaction was propagated during the rescan.
Your environment
- version of
lnd: 0.16.2-beta (exact version unknown)
- operating system: N/A (hosted by Voltage)
- backend: unknown (managed by Voltage)
- any other relevant environment details: N/A
Steps to reproduce
- Run a Lightning Network node using the Voltage service.
- Upgrade the node to version 0.16.x.
- Encounter an invalid transaction of 147 sats that causes on-chain funds to be stuck in Pending state.
- Perform wallet rescans with the help of a Voltage engineer, but the issue persists.
Expected behaviour
The invalid transaction of 147 sats should not affect the on-chain funds, and they should not be stuck in Pending state.
Actual behaviour
The invalid transaction of 147 sats is causing the majority of my on-chain funds to be stuck in Pending state, and the issue persists even after performing wallet rescans.
Background
I am currently running a Lightning Network node using the Voltage service. Due to an invalid transaction of 147 sats, most of my on-chain funds are stuck in Pending state.
A brief history of the issue:
Your environment
lnd: 0.16.2-beta (exact version unknown)Steps to reproduce
Expected behaviour
The invalid transaction of 147 sats should not affect the on-chain funds, and they should not be stuck in Pending state.
Actual behaviour
The invalid transaction of 147 sats is causing the majority of my on-chain funds to be stuck in Pending state, and the issue persists even after performing wallet rescans.