multi: introduce new traffic shaper method.
We introduce a new specific fail resolution error when the external HTLC interceptor denies the incoming HTLC. Moreover we introduce a new traffic shaper method which moves the implementation of asset HTLC to the external layers. Moreover itests are adopted to reflect this new change.
This commit is contained in:
8 files changed
+37
-248
No files matched your search
@@ -508,4 +508,9 @@ type AuxTrafficShaper interface {
|
||||
PaymentBandwidth(htlcBlob, commitmentBlob fn.Option[tlv.Blob],
|
||||
linkBandwidth,
|
||||
htlcAmt lnwire.MilliSatoshi) (lnwire.MilliSatoshi, error)
|
||||
|
||||
// IsCustomHTLC returns true if the HTLC carries the set of relevant
|
||||
// custom records to put it under the purview of the traffic shaper,
|
||||
// meaning that it's from a custom channel.
|
||||
IsCustomHTLC(htlcRecords lnwire.CustomRecords) bool
|
||||
}
|
||||
Reference in new issue
Block a user