pull down to refresh

50 sats \ 3 replies \ @endothermicdev 1 Apr \ on: Zeus mobile node blinded path failure lightning
Do you have inbound liquidity on them in excess of the invoice amount? There's a channel reserve to factor in as well. I assume the olympus node supports the option_route_blinding feature (bits 24/25)? (If it's node id 031b301307574bbe9b9ac7b79cbe1700e31e544513eae0b5d7497483083f99e581 it looks like it's supported.)
Blinded paths are really hard to debug, but usually the difficulty is in diagnosing payment failure with no error information, not in adding a blinded path to the invoice.
write
preview
0 sats \ 2 replies \ @BallLightning OP 1 Apr
Yes I have liquidity. Yes, the node id is the one you referred in your post. Why are you talking about payment failures? As stated above I get error when creating the invoice (maybe payment problems will appear next if I actually manage to create an invoice).
reply
0 sats \ 1 reply \ @endothermicdev 1 Apr
Just giving you more to look forward to once you cross this hurdle =D. Sounds like a bug with Zeus as there doesn't seem to be any protocol related issue here (well, the only other thing is to make sure your channel to olympus is active, but that should be the case.)
reply
0 sats \ 0 replies \ @BallLightning OP 1 Apr
Yeah. It gives the error immediately. I was hoping somebody here would have experience with zeus.
reply