Yong

> why the omni address start with 3? because it's using P2SH, as stated in their docs, > Pay-to-script-hash address support is unlocked as of block #322000 check, https://github.com/OmniLayer/spec#unlocking-features

Could you turn on debug or trace log and share the logs again?

@varg-finance after the `git clone`, you need to check out to the branch with `git checkout remote-log-rebase`, then `make install` should work.

Saw these errors from #6148 too, which was caused by a power outage. Can you share more relevant logs? I'm looking for keywords like `serviceID`, ` added to tor controller`,...

!lightninglabs-deploy mute 2023-Feb-01

Read the logs and found the following line, which shows the payment is still stuck in flight under the new version of `lnd`. ```go 2021-06-22 15:21:36.886 [INF] LTND: Version: 0.13.0-beta...

A possible mitigation is to put a timeout while the router is waiting on `resultChan`. Meanwhile, yeah, we could just mark the old in-flight payments as failed, since their HTLC...

What remains unclear here is, we should have seen the log printed from this [line](https://github.com/lightningnetwork/lnd/blob/master/routing/payment_lifecycle.go#L173) since the call of `CollectResultAsync` is unblocking. Unless `payment, currentState, err := p.fetchPaymentState()` or `shardHandler.checkShards()`...

Chatted with @michael1011 , all the stuck payments happened before the fix, in particular, the stats are, ``` 2020-10-07 00:00:00 : 1 2020-12-20 00:00:00 : 1 2020-12-26 00:00:00 : 1...

> We currently have 676 IN_FLIGHT payments for this node. @miketwenty1 Just to be sure, all these payments should have been marked as failed right?