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
If the app used to pay the JIT channel invoice does prepayment probing it will successfully trigger the htlc_intercepted => OpenChannel event => ChannelReady and attempt to forward the probe. When the app goes to send the actual payment we will get htlc_intercepted again but this time the library will throw an error because the OutboundJITChannelState is not in the AwaitingPayment state anymore.
Haven't looked into best way to handle this.
I think at a high level we will either need to allow htlc_intercepted to happen when the channel is already ready and allow it to be forwarded OR detect the failed probe and rollback channel state so the subsequent htlc can be routed as if it was the first.
The text was updated successfully, but these errors were encountered:
If the app used to pay the JIT channel invoice does prepayment probing it will successfully trigger the htlc_intercepted => OpenChannel event => ChannelReady and attempt to forward the probe. When the app goes to send the actual payment we will get htlc_intercepted again but this time the library will throw an error because the OutboundJITChannelState is not in the AwaitingPayment state anymore.
Haven't looked into best way to handle this.
I think at a high level we will either need to allow htlc_intercepted to happen when the channel is already ready and allow it to be forwarded OR detect the failed probe and rollback channel state so the subsequent htlc can be routed as if it was the first.
The text was updated successfully, but these errors were encountered: