mirror of
https://github.com/lightningnetwork/lnd.git
synced 2025-09-19 12:01:27 +02:00
lnwallet: Simplify updateLog struct by removing redundant pointers.
The updateLog struct contains pointers that refer to the state of the commitment chains. Instead, query the commitments directly.
This commit is contained in:
committed by
Olaoluwa Osuntokun
parent
885753cae4
commit
2b58a39d30
@@ -1026,8 +1026,8 @@ func (l *channelLink) updateChannelFee(feePerKw btcutil.Amount) error {
|
||||
// processLockedInHtlcs serially processes each of the log updates which have
|
||||
// been "locked-in". An HTLC is considered locked-in once it has been fully
|
||||
// committed to in both the remote and local commitment state. Once a channel
|
||||
// updates is locked-in, then it can be acted upon, meaning: settling htlc's,
|
||||
// cancelling them, or forwarding new HTLC's to the next hop.
|
||||
// updates is locked-in, then it can be acted upon, meaning: settling HTLCs,
|
||||
// cancelling them, or forwarding new HTLCs to the next hop.
|
||||
func (l *channelLink) processLockedInHtlcs(
|
||||
paymentDescriptors []*lnwallet.PaymentDescriptor) []*htlcPacket {
|
||||
|
||||
@@ -1080,7 +1080,7 @@ func (l *channelLink) processLockedInHtlcs(
|
||||
l.overflowQueue.SignalFreeSlot()
|
||||
|
||||
// An incoming HTLC add has been full-locked in. As a result we
|
||||
// can no examine the forwarding details of the HTLC, and the
|
||||
// can now examine the forwarding details of the HTLC, and the
|
||||
// HTLC itself to decide if: we should forward it, cancel it,
|
||||
// or are able to settle it (and it adheres to our fee related
|
||||
// constraints).
|
||||
|
Reference in New Issue
Block a user