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
@@ -1121,7 +1121,7 @@ There are 2 main options for synchronizing to chain on startup:
1121
1121
**Full Blocks or BIP 157/158**
1122
1122
1123
1123
If you are connecting full blocks or using BIP 157/158, then it is recommended to use
1124
-
LDK's `lightning_block_sync` sample moduleasin the example above: the high-level steps that must be done for both `ChannelManager` and each `ChannelMonitor` are as follows:
1124
+
LDK's `lightning_block_sync` sample crateasin the example above: the high-level steps that must be done for both `ChannelManager` and each `ChannelMonitor` are as follows:
1125
1125
1126
1126
1. Get the last blockhash that each object saw.
1127
1127
-Receive the latest block hash when through [deserializtion](https://docs.rs/lightning/*/lightning/ln/channelmanager/struct.ChannelManagerReadArgs.html) of the `ChannelManager` via `read()`
@@ -1142,7 +1142,7 @@ Otherwise, you can use LDK's `Confirm` interface directly as in the examples abo
1142
1142
2. Tell LDK what your best known block header and height is.
1143
1143
3. Call `channel_manager_constructor.chain_sync_completed(..)` to complete the initial sync process.
0 commit comments