Merge pull request #5874 from Roasbeef/chan-type-feature-bit-fix

lnwire: switch chan_type feature to bits 44/45
This commit is contained in:
Olaoluwa Osuntokun 2021-10-25 14:19:29 -07:00 committed by GitHub
commit 60a1f2d8d9
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 5 additions and 7 deletions

View file

@ -101,7 +101,9 @@ need to be kept in memory.
initiator to signal their desired channel type to use with the remote peer. If
the remote peer supports said channel type and agrees, the previous implicit
negotiation based on the shared set of feature bits is bypassed, and the
proposed channel type is used.
proposed channel type is used. [Feature bits 44/45 are used to
signal](https://github.com/lightningnetwork/lnd/pull/5874) this new feature.
### Script Enforced Channel Leases

View file

@ -145,19 +145,15 @@ const (
// negotiation methods. With this bit, there is no longer a "default"
// implicit channel commitment type, allowing a connection to
// open/maintain types of several channels over its lifetime.
//
// TODO: Decide on actual feature bit value.
ExplicitChannelTypeRequired = 2020
ExplicitChannelTypeRequired = 44
// ExplicitChannelTypeOptional is an optional bit that denotes that a
// connection established with this node is to use explicit channel
// commitment types for negotiation instead of the existing implicit
// negotiation methods. With this bit, there is no longer a "default"
// implicit channel commitment type, allowing a connection to
// open/maintain types of several channels over its lifetime.
//
// TODO: Decide on actual feature bit value.
ExplicitChannelTypeOptional = 2021
ExplicitChannelTypeOptional = 45
// ScriptEnforcedLeaseOptional is an optional feature bit that signals
// that the node requires channels having zero-fee second-level HTLC