Is your feature request related to a problem? Please describe.
With zero-conf channels / channel aliases it is possible to have channels with channel ID sthat do not represent actual confirmed transactions. This is similar to #18 but also poses additonal problems: some code might assumes that the channel ID encodes the block height, other code might assume that the ID (as long) is a positive number.
Describe the solution you'd like
Channels with a "fake" ID don't confuse lnd-manageJ. Features continue working as expected, height/age information is derived via other means.
Is your feature request related to a problem? Please describe. With zero-conf channels / channel aliases it is possible to have channels with channel ID sthat do not represent actual confirmed transactions. This is similar to #18 but also poses additonal problems: some code might assumes that the channel ID encodes the block height, other code might assume that the ID (as
long
) is a positive number.Describe the solution you'd like Channels with a "fake" ID don't confuse lnd-manageJ. Features continue working as expected, height/age information is derived via other means.
Additional context Example: