mirror of
https://github.com/lightningnetwork/lnd.git
synced 2024-11-19 09:53:54 +01:00
0b4e03f5fc
With go 1.17 a change to the build flags was implemented: https://go.googlesource.com/proposal/+/master/design/draft-gobuild.md The formatter now automatically adds the forward-compatible build tag format and the linter checks for them, so we need to include them in our code.
34 lines
1.4 KiB
Go
34 lines
1.4 KiB
Go
//go:build dev
|
|
// +build dev
|
|
|
|
package lncfg
|
|
|
|
// Legacy is a sub-config that houses all the legacy protocol options. These
|
|
// are mostly used for integration tests as most modern nodes shuld always run
|
|
// with them on by default.
|
|
type LegacyProtocol struct {
|
|
// LegacyOnionFormat if set to true, then we won't signal
|
|
// TLVOnionPayloadOptional. As a result, nodes that include us in the
|
|
// route won't use the new modern onion framing.
|
|
LegacyOnionFormat bool `long:"onion" description:"force node to not advertise the new modern TLV onion format"`
|
|
|
|
// CommitmentTweak guards if we should use the old legacy commitment
|
|
// protocol, or the newer variant that doesn't have a tweak for the
|
|
// remote party's output in the commitment. If set to true, then we
|
|
// won't signal StaticRemoteKeyOptional.
|
|
CommitmentTweak bool `long:"committweak" description:"force node to not advertise the new commitment format"`
|
|
}
|
|
|
|
// LegacyOnion returns true if the old legacy onion format should be used when
|
|
// we're an intermediate or final hop. This controls if we set the
|
|
// TLVOnionPayloadOptional bit or not.
|
|
func (l *LegacyProtocol) LegacyOnion() bool {
|
|
return l.LegacyOnionFormat
|
|
}
|
|
|
|
// NoStaticRemoteKey returns true if the old commitment format with a tweaked
|
|
// remote key should be used for new funded channels.
|
|
func (l *LegacyProtocol) NoStaticRemoteKey() bool {
|
|
return l.CommitmentTweak
|
|
}
|