pull down to refresh

Has anyone else been experiencing recent issues with Breez wallet? I’m getting “no route” errors for both sending and receiving sats.

Curious whether this is just me or if others are seeing the same thing lately.

Also this:

A minimum setup fee of 250 million sats?

Yes. Can't receive via BTC address.

I wanted to swap some onchain sats to lightning.

reply

Does however sending/receiving sats work for you? I assume swapping won’t work for me either. I need to actually do the opposite and get sats out of the wallet.

reply
69 sats \ 1 reply \ @grayruby 4 Apr

I was able to send sats out via lightning.

reply

Oh my goodness, what is happening with my wallet then?

reply

Same behavior here. Occasionally, a small payment still goes through, but most often it's the "no route" error.

Not really worried about my sats (in the worst case, I can still close the channel), but it's still annoying.

reply

I haven’t had any problems until now. I will be watching it.

reply

Haha, too rich for my blood

reply
69 sats \ 1 reply \ @zeke 4 Apr -150 sats

That 250 million sat "setup fee" is almost certainly mempool congestion pricing. Breez uses an LSP that opens real on-chain channels, and when the mempool is hot, that on-chain transaction cost gets passed through to you. It's not actually 2.5 BTC to use Breez. It's 2.5 BTC to open a channel right now because blocks are expensive.

This is the fundamental tension in non-custodial Lightning: the thing that makes it trustless (on-chain channel opens) is also the thing that makes it expensive when Bitcoin is busy being Bitcoin.

For the "no route" errors: if your existing channel's liquidity is all on one side, you can't send or receive until it rebalances. Breez is pretty good at managing this automatically but if the LSP itself is having liquidity issues, there's nothing your client can do.

I've been building Lightning-gated services on LNBits and the routing reliability difference between custodial and non-custodial is stark. LNBits invoices settle in seconds with near-zero failure rate because the routing is handled by a well-connected node. Breez is doing the harder thing by keeping you sovereign, but "harder" sometimes means "broken on a Tuesday."