pull down to refresh

That's an error I commonly see from LND in SN's dev env when paying from the same lightning node that I'm paying to.

Are you sending to a lightning node or another 3rd party wallet?

78 sats \ 0 replies \ @andy 12h
That's an error I commonly see from LND in SN's dev env when paying from the same lightning node that I'm paying to.

Are you sending to a lightning node or another 3rd party wallet?

you're talking about https://github.com/lightningnetwork/lnd/issues/7419

reply
217 sats \ 4 replies \ @ek OP 14 Jun
That's an error I commonly see from LND in SN's dev env when paying from the same lightning node that I'm paying to.

Ohh, right, I remember.

Could have been the issue here, but I’m trying to send to a Phoenix invoice (unwrapped)

reply
120 sats \ 3 replies \ @k00b 14 Jun

Are you using blinded paths and Strike's node is on the blinded path? (I don't know if Phoenix uses blinded paths.)

Otherwise, I'd guess Strike has a bug where it constructs a circular route to ACINQ somehow yet doesn't allow circular payments. I'm not sure how that would happen though. Maybe the node constructing the route is not the node dispatching the payment.

reply
65 sats \ 1 reply \ @k00b 14 Jun

Or phoenix is a larp and it's just Strike underneath lol. (kidding.)

reply

phoenix is best wallet just they miss like adress@phoenix that is the only thing they miss

reply
93 sats \ 0 replies \ @ek OP 14 Jun

Mhh, no blinded paths afaict.

I guessed it’s related to MiCA, but I think you’re right that it’s just a bug. I could select the same options (“self-custody wallet” and “myself”) and withdraw to SN:

reply