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

[bug]: TXs not making it to mempool. #9286

Open
bparker0 opened this issue Nov 20, 2024 · 14 comments
Open

[bug]: TXs not making it to mempool. #9286

bparker0 opened this issue Nov 20, 2024 · 14 comments

Comments

@bparker0
Copy link

Opened some new channels from ThunderHub a couple days ago. Opening TX's are shown in 'lncli pendingchannels' with zero limbo balance. The opening transactions do not show in mempool. I tried force closing them using 'lncli closechannel --force channelpoint n'. Closing TX's do not show in mem pool either. Pending channels shows limbo balances for each respective channel after trying to force close the channels.

  • lnd v0.18.3
  • Linux myNode 5.10.0-0.deb10.16-amd64 1 SMP Debian 5.10.127-2~bpo10+1 (2022-07-28) x86_64 GNU/Linux
  • v27.1.knots20240801
  • ThunderHub v0.13.31
  • Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz with 1 x 512GB M.2 and 1 x 2TB M.2

Not sure how to reproduce the issue, looking for some help. Maybe my only option is to try and manually close all my existing channels and then do '--reset-wallet-transactions' from config file. Wait for it to resync and then abandon the pending channels if they are still showing. Thoughts?

@bparker0 bparker0 added bug Unintended code behaviour needs triage labels Nov 20, 2024
@hieblmi
Copy link
Collaborator

hieblmi commented Nov 20, 2024

Hi @bparker0, thanks for raising this issue.

Could you check if the channel inputs are indeed spent on the block chain. And could you grep the logs for one of the affected channels and post your findings here?

@bparker0
Copy link
Author

bparker0 commented Nov 20, 2024

I'm not sure how I can check if the channel input was spent, it doesn't look anything was broadcasted when I opened or forced closed these channels. You'll have to forgive me here but I'm not as familiar using cli. I'm not even sure which directory myNode keeps the logfiles. Fortunately they provide an easy way to download the entire debug log from the web interface. If you would like I could share the log file with you. I have sifted through and copied one of the affected channels from the LND log file below.

2024-11-19 00:08:16.330 [INF] SRVR: Established connection to: 022d509049e143b1c5fc5383210acb97a3e5a4b0e0d31dd4c920eee92a4aacd312@86.87.162.105:9735
2024-11-19 00:08:16.330 [INF] SRVR: Finalizing connection to 022d509049e143b1c5fc5383210acb97a3e5a4b0e0d31dd4c920eee92a4aacd312@86.87.162.105:9735, inbound=false
2024-11-19 00:08:16.536 [INF] PEER: Peer(022d509049e143b1c5fc5383210acb97a3e5a4b0e0d31dd4c920eee92a4aacd312): Loading ChannelPoint(09d769f2585845d8ced749f6f65b3938ac1da8aa68d12a00d8d54bd26d39e48a:1), isPending=true
2024-11-19 00:08:16.536 [WRN] PEER: Peer(022d509049e143b1c5fc5383210acb97a3e5a4b0e0d31dd4c920eee92a4aacd312): ChannelPoint(09d769f2585845d8ced749f6f65b3938ac1da8aa68d12a00d8d54bd26d39e48a:1) has status ChanStatusBorked|ChanStatusCommitBroadcasted|ChanStatusLocalCloseInitiator, won't start.
2024-11-19 00:08:16.543 [INF] PEER: Peer(022d509049e143b1c5fc5383210acb97a3e5a4b0e0d31dd4c920eee92a4aacd312): Loading ChannelPoint(af2cf574118fa899c5e5a1be8091c52318ceb847dba8c0e793e26461000706d7:0), isPending=true
2024-11-19 00:08:16.543 [WRN] PEER: Peer(022d509049e143b1c5fc5383210acb97a3e5a4b0e0d31dd4c920eee92a4aacd312): ChannelPoint(af2cf574118fa899c5e5a1be8091c52318ceb847dba8c0e793e26461000706d7:0) has status ChanStatusBorked|ChanStatusCommitBroadcasted|ChanStatusLocalCloseInitiator, won't start.
2024-11-19 00:08:16.543 [INF] PEER: Peer(022d509049e143b1c5fc5383210acb97a3e5a4b0e0d31dd4c920eee92a4aacd312): Sending 2 channel sync messages to peer after loading active channels
2024-11-19 00:08:16.543 [INF] PEER: Peer(022d509049e143b1c5fc5383210acb97a3e5a4b0e0d31dd4c920eee92a4aacd312): Negotiated chan series queries
2024-11-19 00:08:16.543 [INF] DISC: Creating new GossipSyncer for peer=022d509049e143b1c5fc5383210acb97a3e5a4b0e0d31dd4c920eee92a4aacd312
2024-11-19 00:08:28.285 [INF] PEER: Peer(022d509049e143b1c5fc5383210acb97a3e5a4b0e0d31dd4c920eee92a4aacd312): unable to read message from peer: read next header: EOF
2024-11-19 00:08:28.285 [INF] PEER: Peer(022d509049e143b1c5fc5383210acb97a3e5a4b0e0d31dd4c920eee92a4aacd312): disconnecting 022d509049e143b1c5fc5383210acb97a3e5a4b0e0d31dd4c920eee92a4aacd312@86.87.162.105:9735, reason: read handler closed
2024-11-19 00:08:28.386 [INF] DISC: Removing GossipSyncer for peer=022d509049e143b1c5fc5383210acb97a3e5a4b0e0d31dd4c920eee92a4aacd312
2024-11-19 00:08:30.917 [INF] SRVR: Established connection to: 022d509049e143b1c5fc5383210acb97a3e5a4b0e0d31dd4c920eee92a4aacd312@86.87.162.105:9735
2024-11-19 00:08:30.917 [INF] SRVR: Finalizing connection to 022d509049e143b1c5fc5383210acb97a3e5a4b0e0d31dd4c920eee92a4aacd312@86.87.162.105:9735, inbound=false
2024-11-19 00:08:31.118 [INF] PEER: Peer(022d509049e143b1c5fc5383210acb97a3e5a4b0e0d31dd4c920eee92a4aacd312): disconnecting 022d509049e143b1c5fc5383210acb97a3e5a4b0e0d31dd4c920eee92a4aacd312@86.87.162.105:9735, reason: unable to start peer: unable to read init msg: read next header: EOF
2024-11-19 00:08:35.944 [INF] SRVR: Finalizing connection to 022d509049e143b1c5fc5383210acb97a3e5a4b0e0d31dd4c920eee92a4aacd312@86.87.162.105:39518, inbound=true
2024-11-19 00:08:35.946 [INF] PEER: Peer(022d509049e143b1c5fc5383210acb97a3e5a4b0e0d31dd4c920eee92a4aacd312): Loading ChannelPoint(09d769f2585845d8ced749f6f65b3938ac1da8aa68d12a00d8d54bd26d39e48a:1), isPending=true
2024-11-19 00:08:35.946 [WRN] PEER: Peer(022d509049e143b1c5fc5383210acb97a3e5a4b0e0d31dd4c920eee92a4aacd312): ChannelPoint(09d769f2585845d8ced749f6f65b3938ac1da8aa68d12a00d8d54bd26d39e48a:1) has status ChanStatusBorked|ChanStatusCommitBroadcasted|ChanStatusLocalCloseInitiator, won't start.
2024-11-19 00:08:35.948 [INF] PEER: Peer(022d509049e143b1c5fc5383210acb97a3e5a4b0e0d31dd4c920eee92a4aacd312): Loading ChannelPoint(af2cf574118fa899c5e5a1be8091c52318ceb847dba8c0e793e26461000706d7:0), isPending=true
2024-11-19 00:08:35.948 [WRN] PEER: Peer(022d509049e143b1c5fc5383210acb97a3e5a4b0e0d31dd4c920eee92a4aacd312): ChannelPoint(af2cf574118fa899c5e5a1be8091c52318ceb847dba8c0e793e26461000706d7:0) has status ChanStatusBorked|ChanStatusCommitBroadcasted|ChanStatusLocalCloseInitiator, won't start.
2024-11-19 00:08:35.948 [INF] PEER: Peer(022d509049e143b1c5fc5383210acb97a3e5a4b0e0d31dd4c920eee92a4aacd312): Sending 2 channel sync messages to peer after loading active channels
2024-11-19 00:08:35.949 [INF] PEER: Peer(022d509049e143b1c5fc5383210acb97a3e5a4b0e0d31dd4c920eee92a4aacd312): Negotiated chan series queries
2024-11-19 00:08:35.949 [INF] DISC: Creating new GossipSyncer for peer=022d509049e143b1c5fc5383210acb97a3e5a4b0e0d31dd4c920eee92a4aacd312
2024-11-19 07:44:33.385 [INF] DISC: GossipSyncer(022d509049e143b1c5fc5383210acb97a3e5a4b0e0d31dd4c920eee92a4aacd312): applying gossipFilter(start=2024-11-19 07:44:33.385651082 -0800 PST m=+225689.583668098, end=2160-12-26 14:12:48.385651082 -0800 PST)
2024-11-19 07:44:33.583 [ERR] DISC: Skewed timestamp (1901350634) for edge policy of short_chan_id(717789778064113665), timestamp too far in the future: peer=022d509049e143b1c5fc5383210acb97a3e5a4b0e0d31dd4c920eee92a4aacd312@86.87.162.105:39518, msg=ChannelUpdate, is_remote=true
2024-11-19 07:44:33.782 [ERR] DISC: Skewed timestamp (1901350892) for edge policy of short_chan_id(771851665200054273), timestamp too far in the future: peer=022d509049e143b1c5fc5383210acb97a3e5a4b0e0d31dd4c920eee92a4aacd312@86.87.162.105:39518, msg=ChannelUpdate, is_remote=true
2024-11-19 07:44:33.783 [ERR] DISC: Skewed timestamp (1901351937) for edge policy of short_chan_id(770697177947439104), timestamp too far in the future: peer=022d509049e143b1c5fc5383210acb97a3e5a4b0e0d31dd4c920eee92a4aacd312@86.87.162.105:39518, msg=ChannelUpdate, is_remote=true
2024-11-19 08:04:33.385 [INF] DISC: GossipSyncer(022d509049e143b1c5fc5383210acb97a3e5a4b0e0d31dd4c920eee92a4aacd312): applying gossipFilter(start=0001-01-01 00:00:00 +0000 UTC, end=0001-01-01 00:00:00 +0000 UTC)
2024-11-19 09:37:05.949 [WRN] PEER: Peer(022d509049e143b1c5fc5383210acb97a3e5a4b0e0d31dd4c920eee92a4aacd312): pong response failure for 022d509049e143b1c5fc5383210acb97a3e5a4b0e0d31dd4c920eee92a4aacd312@86.87.162.105:39518: timeout while waiting for pong response -- disconnecting
2024-11-19 09:37:05.950 [INF] PEER: Peer(022d509049e143b1c5fc5383210acb97a3e5a4b0e0d31dd4c920eee92a4aacd312): disconnecting 022d509049e143b1c5fc5383210acb97a3e5a4b0e0d31dd4c920eee92a4aacd312@86.87.162.105:39518, reason: pong response failure for 022d509049e143b1c5fc5383210acb97a3e5a4b0e0d31dd4c920eee92a4aacd312@86.87.162.105:39518: timeout while waiting for pong response -- disconnecting
2024-11-19 09:37:05.950 [INF] PEER: Peer(022d509049e143b1c5fc5383210acb97a3e5a4b0e0d31dd4c920eee92a4aacd312): unable to read message from peer: read next header: read tcp 192.168.8.221:9735->86.87.162.105:39518: use of closed network connection
2024-11-19 09:37:06.051 [INF] DISC: Removing GossipSyncer for peer=022d509049e143b1c5fc5383210acb97a3e5a4b0e0d31dd4c920eee92a4aacd312
2024-11-19 09:37:49.148 [INF] SRVR: Finalizing connection to 022d509049e143b1c5fc5383210acb97a3e5a4b0e0d31dd4c920eee92a4aacd312@86.87.162.105:56374, inbound=true
2024-11-19 09:37:49.359 [INF] PEER: Peer(022d509049e143b1c5fc5383210acb97a3e5a4b0e0d31dd4c920eee92a4aacd312): Loading ChannelPoint(09d769f2585845d8ced749f6f65b3938ac1da8aa68d12a00d8d54bd26d39e48a:1), isPending=true
2024-11-19 09:37:49.359 [WRN] PEER: Peer(022d509049e143b1c5fc5383210acb97a3e5a4b0e0d31dd4c920eee92a4aacd312): ChannelPoint(09d769f2585845d8ced749f6f65b3938ac1da8aa68d12a00d8d54bd26d39e48a:1) has status ChanStatusBorked|ChanStatusCommitBroadcasted|ChanStatusLocalCloseInitiator, won't start.
2024-11-19 09:37:49.369 [INF] PEER: Peer(022d509049e143b1c5fc5383210acb97a3e5a4b0e0d31dd4c920eee92a4aacd312): Loading ChannelPoint(af2cf574118fa899c5e5a1be8091c52318ceb847dba8c0e793e26461000706d7:0), isPending=true
2024-11-19 09:37:49.369 [WRN] PEER: Peer(022d509049e143b1c5fc5383210acb97a3e5a4b0e0d31dd4c920eee92a4aacd312): ChannelPoint(af2cf574118fa899c5e5a1be8091c52318ceb847dba8c0e793e26461000706d7:0) has status ChanStatusBorked|ChanStatusCommitBroadcasted|ChanStatusLocalCloseInitiator, won't start.
2024-11-19 09:37:49.369 [INF] PEER: Peer(022d509049e143b1c5fc5383210acb97a3e5a4b0e0d31dd4c920eee92a4aacd312): Sending 2 channel sync messages to peer after loading active channels
2024-11-19 09:37:49.369 [INF] PEER: Peer(022d509049e143b1c5fc5383210acb97a3e5a4b0e0d31dd4c920eee92a4aacd312): Negotiated chan series queries
2024-11-19 09:37:49.370 [INF] DISC: Creating new GossipSyncer for peer=022d509049e143b1c5fc5383210acb97a3e5a4b0e0d31dd4c920eee92a4aacd312
2024-11-19 10:44:33.386 [INF] DISC: GossipSyncer(022d509049e143b1c5fc5383210acb97a3e5a4b0e0d31dd4c920eee92a4aacd312): applying gossipFilter(start=2024-11-19 10:44:33.386350974 -0800 PST m=+236489.584367994, end=2160-12-26 17:12:48.386350974 -0800 PST)
2024-11-19 10:44:33.589 [ERR] DISC: Skewed timestamp (1901350634) for edge policy of short_chan_id(717789778064113665), timestamp too far in the future: peer=022d509049e143b1c5fc5383210acb97a3e5a4b0e0d31dd4c920eee92a4aacd312@86.87.162.105:56374, msg=ChannelUpdate, is_remote=true
2024-11-19 10:44:33.822 [ERR] DISC: Skewed timestamp (1901350892) for edge policy of short_chan_id(771851665200054273), timestamp too far in the future: peer=022d509049e143b1c5fc5383210acb97a3e5a4b0e0d31dd4c920eee92a4aacd312@86.87.162.105:56374, msg=ChannelUpdate, is_remote=true
2024-11-19 10:44:33.827 [ERR] DISC: Skewed timestamp (1901351937) for edge policy of short_chan_id(770697177947439104), timestamp too far in the future: peer=022d509049e143b1c5fc5383210acb97a3e5a4b0e0d31dd4c920eee92a4aacd312@86.87.162.105:56374, msg=ChannelUpdate, is_remote=true
2024-11-19 11:04:33.385 [INF] DISC: GossipSyncer(022d509049e143b1c5fc5383210acb97a3e5a4b0e0d31dd4c920eee92a4aacd312): applying gossipFilter(start=0001-01-01 00:00:00 +0000 UTC, end=0001-01-01 00:00:00 +0000 UTC)
2024-11-19 15:51:41.650 [WRN] FNDG: fundingManager shutting down, stopping funding flow for ChannelPoint(09d769f2585845d8ced749f6f65b3938ac1da8aa68d12a00d8d54bd26d39e48a:1)
2024-11-19 15:51:41.650 [ERR] FNDG: Unable to advance pending state of ChannelPoint(09d769f2585845d8ced749f6f65b3938ac1da8aa68d12a00d8d54bd26d39e48a:1): error waiting for funding confirmation for ChannelPoint(09d769f2585845d8ced749f6f65b3938ac1da8aa68d12a00d8d54bd26d39e48a:1): funding manager shutting down
2024-11-19 15:51:41.694 [INF] SRVR: Disconnecting from 022d509049e143b1c5fc5383210acb97a3e5a4b0e0d31dd4c920eee92a4aacd312@86.87.162.105:56374
2024-11-19 15:51:41.694 [INF] PEER: Peer(022d509049e143b1c5fc5383210acb97a3e5a4b0e0d31dd4c920eee92a4aacd312): disconnecting 022d509049e143b1c5fc5383210acb97a3e5a4b0e0d31dd4c920eee92a4aacd312@86.87.162.105:56374, reason: server: DisconnectPeer called
2024-11-19 15:51:41.694 [INF] PEER: Peer(022d509049e143b1c5fc5383210acb97a3e5a4b0e0d31dd4c920eee92a4aacd312): unable to read message from peer: read next header: read tcp 192.168.8.221:9735->86.87.162.105:56374: use of closed network connection
2024-11-19 15:55:51.141 [INF] SRVR: Finalizing connection to 022d509049e143b1c5fc5383210acb97a3e5a4b0e0d31dd4c920eee92a4aacd312@86.87.162.105:9735, inbound=false
2024-11-19 15:55:51.347 [INF] PEER: Peer(022d509049e143b1c5fc5383210acb97a3e5a4b0e0d31dd4c920eee92a4aacd312): Loading ChannelPoint(09d769f2585845d8ced749f6f65b3938ac1da8aa68d12a00d8d54bd26d39e48a:1), isPending=true
2024-11-19 15:55:51.347 [WRN] PEER: Peer(022d509049e143b1c5fc5383210acb97a3e5a4b0e0d31dd4c920eee92a4aacd312): ChannelPoint(09d769f2585845d8ced749f6f65b3938ac1da8aa68d12a00d8d54bd26d39e48a:1) has status ChanStatusBorked|ChanStatusCommitBroadcasted|ChanStatusLocalCloseInitiator, won't start.
2024-11-19 15:55:51.349 [INF] PEER: Peer(022d509049e143b1c5fc5383210acb97a3e5a4b0e0d31dd4c920eee92a4aacd312): Loading ChannelPoint(af2cf574118fa899c5e5a1be8091c52318ceb847dba8c0e793e26461000706d7:0), isPending=true
2024-11-19 15:55:51.349 [WRN] PEER: Peer(022d509049e143b1c5fc5383210acb97a3e5a4b0e0d31dd4c920eee92a4aacd312): ChannelPoint(af2cf574118fa899c5e5a1be8091c52318ceb847dba8c0e793e26461000706d7:0) has status ChanStatusBorked|ChanStatusCommitBroadcasted|ChanStatusLocalCloseInitiator, won't start.
2024-11-19 15:55:51.349 [INF] PEER: Peer(022d509049e143b1c5fc5383210acb97a3e5a4b0e0d31dd4c920eee92a4aacd312): Sending 2 channel sync messages to peer after loading active channels
2024-11-19 15:55:51.349 [INF] PEER: Peer(022d509049e143b1c5fc5383210acb97a3e5a4b0e0d31dd4c920eee92a4aacd312): Negotiated chan series queries
2024-11-19 15:55:51.349 [INF] DISC: Creating new GossipSyncer for peer=022d509049e143b1c5fc5383210acb97a3e5a4b0e0d31dd4c920eee92a4aacd312

@hieblmi
Copy link
Collaborator

hieblmi commented Nov 20, 2024

Thanks @bparker0, indeed the channel points don't exist on-chain, I don't see what went wrong during channel openings from the log snippet. Could you send me the entire log to hieblmi @ lightning.engineering?

Also, could you check if your on-chain balance hasn't changed through the channel openings, meaning, do you see the on-chain balance that you expect or is something missing?

@saubyk saubyk added troubleshooting and removed bug Unintended code behaviour needs triage labels Nov 20, 2024
@Roasbeef
Copy link
Member

v27.1.knots20240801

Can you report your Knots config? We've had some instances in the past of a popular guide having issues in its mempool related config.

@hieblmi
Copy link
Collaborator

hieblmi commented Nov 20, 2024

potentially related issue: #9048

This issue was fixed with knots version 27.1.3

@bparker0
Copy link
Author

Ok, I just got home from work. Just sent the log file via wetransfer.com, hopefully that works. It's 8MB in size. Knots is running whatever the default config is at installation. I installed knots from the myNode web interface.

@bparker0
Copy link
Author

The onchain balance has fluctuated considerably over that last week. Although, I did just force close a 5M sat channel with a node that had been offline for quite sometime. It's been about 11 days since I closed it.

@bparker0
Copy link
Author

I have seen the onchain balance increase by as much as 10M sats during this force close. It seems that I have 5M more sats than what I had originally put in this wallet. Maybe somehow I ended up with the other nodes sats. I'll give it another week for the funds to straighten out. If this is the case I would like to return the sats. The fun part is going to be trying to contact the node runner.

@hieblmi
Copy link
Collaborator

hieblmi commented Nov 21, 2024

@bparker0 are you also able to provide the output of lncli pendingchannels here if you have access to the cli?

From the logs you sent I can see that the channels that you are trying to force close...

2024-11-19 20:56:19.313 [INF] CNCT: Re-publishing force close tx(5d959b9548abbc955ca1eb672b2792bac7632d354b46aedff99db2c9375fba7e) for channel 09d769f2585845d8ced749f6f65b3938ac1da8aa68d12a00d8d54bd26d39e48a:1
2024-11-19 20:56:19.314 [ERR] BTCN: Broadcast attempt failed: <nil>
2024-11-19 20:56:19.314 [WRN] BTWL: Transaction 5d959b9548abbc955ca1eb672b2792bac7632d354b46aedff99db2c9375fba7e not accepted by mempool: missing-inputs
2024-11-19 20:56:19.314 [INF] CNCT: Re-publishing force close tx(ae6988ee9db1ac9cf4eb60843b04fd9685b0eebc0795db0d6e092f20d335dd82) for channel af2cf574118fa899c5e5a1be8091c52318ceb847dba8c0e793e26461000706d7:0
2024-11-19 20:56:19.315 [ERR] BTCN: Broadcast attempt failed: <nil>
2024-11-19 20:56:19.316 [WRN] BTWL: Transaction ae6988ee9db1ac9cf4eb60843b04fd9685b0eebc0795db0d6e092f20d335dd82 not accepted by mempool: missing-inputs
2024-11-19 20:56:19.316 [INF] CNCT: Re-publishing force close tx(d0eb4dc8b50adb2af06aed3ddcd129d2562f78c7e283c5af5555cb77b2f820ba) for channel b0c646c1bd6c31a529e689eb0f506094e0238988e1ec1371c6d7c573451ae410:0

...never made it on-chain because the input da3cc6122545c91dc0288bf69d9ca471b324701cfc948b510829a24591cfe2d5:1 that they all try to use for funding has already been used for a different channel opening here: https://mempool.space/address/bc1pphuxurr0wyjayecasskt438pjh9uug3lzsdxuscavqme6actkhnsu6r48a

The logs you sent unfortunately don't contain the channel open messages for these points, they must've happened before the log starts.

Once again, would be good to see what lncli pendingchannels says.

@bparker0
Copy link
Author

bparker0 commented Nov 21, 2024

lncli pendingchannels
{
    "total_limbo_balance":  "7989590",
    "pending_open_channels":  [],
    "pending_closing_channels":  [],
    "pending_force_closing_channels":  [],
    "waiting_close_channels":  [
        {
            "channel":  {
                "remote_node_pub":  "022d509049e143b1c5fc5383210acb97a3e5a4b0e0d31dd4c920eee92a4aacd312",
                "channel_point":  "09d769f2585845d8ced749f6f65b3938ac1da8aa68d12a00d8d54bd26d39e48a:1",
                "capacity":  "4000000",
                "local_balance":  "3996530",
                "remote_balance":  "0",
                "local_chan_reserve_sat":  "40000",
                "remote_chan_reserve_sat":  "40000",
                "initiator":  "INITIATOR_LOCAL",
                "commitment_type":  "ANCHORS",
                "num_forwarding_packages":  "0",
                "chan_status_flags":  "ChanStatusBorked|ChanStatusCommitBroadcasted|ChanStatusLocalCloseInitiator",
                "private":  false,
                "memo":  ""
            },
            "limbo_balance":  "3996530",
            "commitments":  {
                "local_txid":  "5d959b9548abbc955ca1eb672b2792bac7632d354b46aedff99db2c9375fba7e",
                "remote_txid":  "15cffd998acbfd755af39d0cef4eb396871c2ef4fd5423db7fb2bebc5088b6dd",
                "remote_pending_txid":  "",
                "local_commit_fee_sat":  "2810",
                "remote_commit_fee_sat":  "2810",
                "remote_pending_commit_fee_sat":  "0"
            },
            "closing_txid":  "5d959b9548abbc955ca1eb672b2792bac7632d354b46aedff99db2c9375fba7e",
            "closing_tx_hex":  ""
        },
        {
            "channel":  {
                "remote_node_pub":  "022d509049e143b1c5fc5383210acb97a3e5a4b0e0d31dd4c920eee92a4aacd312",
                "channel_point":  "af2cf574118fa899c5e5a1be8091c52318ceb847dba8c0e793e26461000706d7:0",
                "capacity":  "2000000",
                "local_balance":  "1996530",
                "remote_balance":  "0",
                "local_chan_reserve_sat":  "20000",
                "remote_chan_reserve_sat":  "20000",
                "initiator":  "INITIATOR_LOCAL",
                "commitment_type":  "ANCHORS",
                "num_forwarding_packages":  "0",
                "chan_status_flags":  "ChanStatusBorked|ChanStatusCommitBroadcasted|ChanStatusLocalCloseInitiator",
                "private":  false,
                "memo":  ""
            },
            "limbo_balance":  "1996530",
            "commitments":  {
                "local_txid":  "ae6988ee9db1ac9cf4eb60843b04fd9685b0eebc0795db0d6e092f20d335dd82",
                "remote_txid":  "85ee7f235a6d05c6634871fbc5ecba5220ff88ce519eb438e76bc9359f49d69b",
                "remote_pending_txid":  "",
                "local_commit_fee_sat":  "2810",
                "remote_commit_fee_sat":  "2810",
                "remote_pending_commit_fee_sat":  "0"
            },
            "closing_txid":  "ae6988ee9db1ac9cf4eb60843b04fd9685b0eebc0795db0d6e092f20d335dd82",
            "closing_tx_hex":  ""
        },
        {
            "channel":  {
                "remote_node_pub":  "026e7f90f4fb31933b20187790c4b8407149f9386a87cd615c0d41dd258e87202c",
                "channel_point":  "b0c646c1bd6c31a529e689eb0f506094e0238988e1ec1371c6d7c573451ae410:0",
                "capacity":  "2000000",
                "local_balance":  "1996530",
                "remote_balance":  "0",
                "local_chan_reserve_sat":  "20000",
                "remote_chan_reserve_sat":  "20000",
                "initiator":  "INITIATOR_LOCAL",
                "commitment_type":  "ANCHORS",
                "num_forwarding_packages":  "0",
                "chan_status_flags":  "ChanStatusBorked|ChanStatusCommitBroadcasted|ChanStatusLocalCloseInitiator",
                "private":  false,
                "memo":  ""
            },
            "limbo_balance":  "1996530",
            "commitments":  {

@hieblmi
Copy link
Collaborator

hieblmi commented Nov 21, 2024

It seems that I have 5M more sats than what I had originally put in this wallet. Maybe somehow I ended up with the other nodes sats.

It should be the case that the pending balance is what is too much in your wallet, 7989590 sats, can you confirm.

All three channels can be abandoned because their funding input was already spent in another channel that you opened,
namely here https://mempool.space/lightning/channel/955718596691623936.

If you can confirm all above then you can abandon the 3 channels.

@bparker0
Copy link
Author

bparker0 commented Nov 22, 2024 via email

@hieblmi
Copy link
Collaborator

hieblmi commented Nov 22, 2024

The inputs of these three channels can be found in the funding transactions that lnd tries to broadcast after a restart. For the first channel, search the log for

2024-11-19 20:56:18.641 [WRN] BTWL: Transaction 09d769f2585845d8ced749f6f65b3938ac1da8aa68d12a00d8d54bd26d39e48a not accepted by mempool: missing-inputs
2024-11-19 20:56:18.641 [ERR] FNDG: Unable to rebroadcast funding tx 02000000000101d5e2cf9145a22908518b94fc1c7024b371a49c9df68b28c01dc9452512c63cda0100000000000000000267790e00000000002251201dfac4c255c47e9762ec3305ac910ebdcdfd3037afcbea7b925c1b5f6558dc9900093d00000000002200204ed737c120cc93d23f0e63fa524a5ebbc920473c6f227ff84501463c8c8b609301408cfb815890139ce3bd472b28e992ebf5979bd47323ce4fdcf73658996390fd0afc86f7afe0cfbf6d0adb19837e81b74248c979e239b9e6ecadc5e4362edf9d6200000000 for ChannelPoint(09d769f2585845d8ced749f6f65b3938ac1da8aa68d12a00d8d54bd26d39e48a:1): transaction rejected: output already spent
2024-11-19 20:56:18.641 [INF] NTFN: New confirmation subscription: conf_id=1, txid=09d769f2585845d8ced749f6f65b3938ac1da8aa68d12a00d8d54bd26d39e48a, num_confs=3 height_hint=871143

If you

bitcoin-cli decoderawtransaction 02000000000101d5e2cf9145a22908518b94fc1c7024b371a49c9df68b28c01dc9452512c63cda0100000000000000000267790e00000000002251201dfac4c255c47e9762ec3305ac910ebdcdfd3037afcbea7b925c1b5f6558dc9900093d00000000002200204ed737c120cc93d23f0e63fa524a5ebbc920473c6f227ff84501463c8c8b609301408cfb815890139ce3bd472b28e992ebf5979bd47323ce4fdcf73658996390fd0afc86f7afe0cfbf6d0adb19837e81b74248c979e239b9e6ecadc5e4362edf9d6200000000

you find the input

"vin": [
    {
      "txid": "da3cc6122545c91dc0288bf69d9ca471b324701cfc948b510829a24591cfe2d5",
      "vout": 1,

that all three channels try to use, but it is already used in the channel I mentioned.

Unfortunately the logs you sent start on 2024-11-19 00:07:50.225 so I can't really see what happened when you opened these channels initially.

@bparker0
Copy link
Author

bparker0 commented Nov 23, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants