You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While LDK's ChannelManager doesn't have immediate access to gossip data, LDK Node does.
We therefore at least could consider to add additional (gossip) data fields to the ChannelDetails returned from list_channel, e.g., the counterparty's node announcement, allowing the user to access the node alias for displaying purposes.
The text was updated successfully, but these errors were encountered:
Mh, thinking about it again it's pretty tricky to this reliably on 'mostly-offline' nodes such as mobile devices, as RGS won't ship us any node announcements. So the optional field in ChannelDetails would be very unreliable, and only populated after we happen to receive a rebroadcast of our counterparty's node announcement.
While LDK's
ChannelManager
doesn't have immediate access to gossip data, LDK Node does.We therefore at least could consider to add additional (gossip) data fields to the
ChannelDetails
returned fromlist_channel
, e.g., the counterparty's node announcement, allowing the user to access the node alias for displaying purposes.The text was updated successfully, but these errors were encountered: