Skip to content

Commit 0eab9ec

Browse files
committed
f - Explain why block events need to be sent to ChannelManager and ChainMonitor
1 parent e5ca8be commit 0eab9ec

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

docs/blockdata.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -42,7 +42,8 @@ At this point, LDK needs to be fed chain data of interest so that it can respond
4242
accordingly. It supports receiving either full blocks or pre-filtered blocks.
4343
Block data can sourced from anywhere, but it is your responsibility to ensure
4444
that the necessary `block_connected` and `block_disconnected` methods are called
45-
on `ChannelManager` and `ChainMonitor`.
45+
on `ChannelManager` and `ChainMonitor`. This allows them to update channel state
46+
and respond to on-chain events, respectively.
4647

4748
LDK comes with a `lightning-block-sync` utility that handles polling a block
4849
source for the best chain tip, detecting chain forks, and notifying listeners

0 commit comments

Comments
 (0)