Expand description
The top-level channel management and payment tracking stuff lives here.
The ChannelManager
is the main chunk of logic implementing the lightning protocol and is
responsible for tracking which channels are open, HTLCs are in flight and reestablishing those
upon reconnect to the relevant peer(s).
It does not manage routing logic (see Router
for that) nor does it manage constructing
on-chain transactions (it only monitors the chain to watch for any force-closes that might
imply it needs to fail HTLCs/payments/channels it manages).
Structs§
- Blinded
Forward - Information used to forward or fail this HTLC that is being forwarded within a blinded path.
- Bolt11
Invoice Parameters - Parameters used with
create_bolt11_invoice
. - Chain
Parameters - Chain-related parameters used to construct a new
ChannelManager
. - Channel
Manager - A lightning node’s channel state machine and payment management logic, which facilitates sending, forwarding, and receiving payments through lightning channels.
- Channel
Manager Read Args - Arguments for the creation of a ChannelManager that are not deserialized.
- Intercept
Id - An identifier used to uniquely identify an intercepted HTLC to LDK.
- Payment
Id - A user-provided identifier in
ChannelManager::send_payment
used to uniquely identify a payment and ensure idempotency in LDK. - PendingHTLC
Info - Information about an incoming HTLC, including the
PendingHTLCRouting
describing where it should go next. - Phantom
Route Hints - Route hints used in constructing invoices for [phantom node payents].
- Recipient
Onion Fields - Information which is provided, encrypted, to the payment recipient when sending HTLCs.
Enums§
- Blinded
Failure - Whether this blinded HTLC is being failed backwards by the introduction node or a blinded node, which determines the failure message that should be used.
- Bolt12
Payment Error - An error when attempting to pay a
Bolt12Invoice
. - Failure
Code - This enum is used to specify which error data to send to peers when failing back an HTLC
using
ChannelManager::fail_htlc_backwards_with_reason
. - PendingHTLC
Routing - Information about where a received HTLC(’s onion) has indicated the HTLC should go.
- Probe
Send Failure - Indicates that we failed to send a payment probe. Further errors may be surfaced later via
Event::ProbeFailed
. - Recent
Payment Details - Used by
ChannelManager::list_recent_payments
to express the status of recent payments. These include payments that have yet to find a successful path, or have unresolved HTLCs. - Retry
- Strategies available to retry payment path failures.
- Retryable
Send Failure - Indicates an immediate error on
ChannelManager::send_payment
. Further errors may be surfaced later viaEvent::PaymentPathFailed
andEvent::PaymentFailed
.
Constants§
- BREAKDOWN_
TIMEOUT - The amount of time in blocks we require our counterparty wait to claim their money (ie time between when we, or our watchtower, must check for them having broadcast a theft transaction).
- MAX_
SHORT_ LIVED_ RELATIVE_ EXPIRY - The maximum expiration from the current time where an
Offer
orRefund
is considered short-lived, while anything with a greater expiration is considered long-lived. - MIN_
CLTV_ EXPIRY_ DELTA - The minimum number of blocks between an inbound HTLC’s CLTV and the corresponding outbound HTLC’s CLTV. The current default represents roughly seven hours of blocks at six blocks/hour.
- MIN_
FINAL_ CLTV_ EXPIRY_ DELTA - Minimum CLTV difference between the current block height and received inbound payments.
Invoices generated for payment to us must set their
min_final_cltv_expiry_delta
field to at least this value.
Traits§
- AChannel
Manager - A trivial trait which describes any
ChannelManager
. - Verification
- A trait defining behavior for creating and verifing the HMAC for authenticating a given data.
Functions§
- provided_
init_ features - Fetches the set of
InitFeatures
flags that are provided by or required byChannelManager
.
Type Aliases§
- Simple
ArcChannel Manager Non- c_bindings
SimpleArcChannelManager
is useful when you need aChannelManager
with a static lifetime, e.g. when you’re usinglightning-net-tokio
(sincetokio::spawn
requires parameters with static lifetimes). Other times you can afford a reference, which is more efficient, in which caseSimpleRefChannelManager
is the more appropriate type. Defining these type aliases prevents issues such as overly long function definitions. Note that theChannelManager
can take any type that implementsNodeSigner
,EntropySource
, andSignerProvider
for its keys manager, or, respectively,Router
for its router, but this type alias chooses the concrete types ofKeysManager
andDefaultRouter
.- Simple
RefChannel Manager Non- c_bindings
SimpleRefChannelManager
is a type alias for a ChannelManager reference, and is the reference counterpart to theSimpleArcChannelManager
type alias. Use this type by default when you don’t need a ChannelManager with a static lifetime. You’ll need a static lifetime in cases such as usage of lightning-net-tokio (sincetokio::spawn
requires parameters with static lifetimes). But if this is not necessary, using a reference is more efficient. Defining these type aliases issues such as overly long function definitions. Note that the ChannelManager can take any type that implementsNodeSigner
,EntropySource
, andSignerProvider
for its keys manager, or, respectively,Router
for its router, but this type alias chooses the concrete types ofKeysManager
andDefaultRouter
.