You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We regularly get users reporting issues with block sync (cause our API is a bit confusing, which desperately needs fixing by exposing the block sync crates to bindings users). These are quite hard to debug from our logs as our logs just aren't super detailed. We should log txids connected/confirmed as long as the list is small-ish, and maybe also log when we add things to the filter.
Go for it. Should require carefully reading the block and transaction connection codepaths from ChannelManager and ChainMonitor all the way down and just ensuring that everything that happens gets logged but only once.
Could i get more information about codepath from channelManager and Chainmonitor , and how channelmaanger is accesing txids from chainmonitor .
and also here 'txid' mentioned here is transaction id of funding transaction?
Ok ,
during constructing a channel message flow is - alice : open_channel , Bob : accept channel, alice : funding_created , bob : funding_signed and after funding_signed message funding_transaction broadcasted . so i have to log after funding signed message .
This issue is about the block connection, though, not the message handling flow. Block connection happens via transactions_confirmed/transactions_unconfirmed/block_connected/block_disconnected.
Hi! I see this issue has been stale for a while. I'm a Summer of Bitcoin applicant and I'd like to pick this up and finish the work started by the previous contributor. I'll start by investigating the block_connected paths in ChannelManager. Is it okay if I take this over?
Hi! I’m interested in working on this issue as part of my Bitcoin open-source learning.
Could you please confirm if it’s still open and point me to relevant files?
Thanks!
Activity
Sharmalm commentedon Sep 3, 2023
can i try this one?
TheBlueMatt commentedon Sep 3, 2023
Go for it. Should require carefully reading the block and transaction connection codepaths from ChannelManager and ChainMonitor all the way down and just ensuring that everything that happens gets logged but only once.
Sharmalm commentedon Sep 5, 2023
Could i get more information about codepath from
channelManagerandChainmonitor, and howchannelmaangeris accesing txids fromchainmonitor.and also here 'txid' mentioned here is transaction id of funding transaction?
TheBlueMatt commentedon Sep 5, 2023
They're fully separate, called independently from LDK users' code.
Sharmalm commentedon Sep 7, 2023
Ok ,
during constructing a channel message flow is - alice :
open_channel, Bob :accept channel, alice :funding_created, bob :funding_signedand afterfunding_signedmessagefunding_transactionbroadcasted . so i have to log afterfunding signedmessage .TheBlueMatt commentedon Sep 7, 2023
This issue is about the block connection, though, not the message handling flow. Block connection happens via
transactions_confirmed/transactions_unconfirmed/block_connected/block_disconnected.Improving block conenction logging and filtered txids
Improving block conenction logging and filtered txids
Improving block conenction logging and filtered txids
Improving block conenction logging and filtered txids
Improving block conenction logging and filtered txids
Improving block conenction logging and filtered txids
malsomesh9 commentedon Jan 31, 2026
Hi! I see this issue has been stale for a while. I'm a Summer of Bitcoin applicant and I'd like to pick this up and finish the work started by the previous contributor. I'll start by investigating the block_connected paths in ChannelManager. Is it okay if I take this over?
malsomesh9 commentedon Feb 1, 2026
Hi! I’m interested in working on this issue as part of my Bitcoin open-source learning.
Could you please confirm if it’s still open and point me to relevant files?
Thanks!
channelmanager: improve block connection logging for easier debugging. …