Expose chan type in `Event::OpenChannelRequest` & `ChannelDetails`
authorMatt Corallo <git@bluematt.me>
Wed, 16 Feb 2022 04:21:29 +0000 (04:21 +0000)
committerMatt Corallo <git@bluematt.me>
Sun, 27 Mar 2022 17:12:17 +0000 (17:12 +0000)
commitb42ebd892b161e846cd37e0bb3639cca9b6c08b8
treec38c9398958306913f8bbe43fc82bcf0c22fe69a
parent41fb56b5befa89309ba0fcaa23bcae31b5beb368
Expose chan type in `Event::OpenChannelRequest` & `ChannelDetails`

As we add new supported channel types, inbound channels which use
new features may cause backwards-compatibility issues for clients.
If a new channel is opened using new features while a client still
wishes to ensure support for downgrading to a previous version of
LDK, that new channel may cause the `ChannelManager` to fail
deserialization due to unsupported feature flags.

By exposing the channel type flags to the user in channel requests,
users wishing to support downgrading to previous versions of LDK
can reject channels which use channel features which previous
versions of LDK do not understand.
fuzz/src/router.rs
lightning/src/ln/channel.rs
lightning/src/ln/channelmanager.rs
lightning/src/routing/router.rs
lightning/src/util/events.rs