Not sure I understand... You don't need to create channels in Breez, it creates them for you.
What was difficult about Breez?
The key to scaling Lightning β‘οΈ is to make it more versatile, and versatility comes from integrating it into more apps π©βπ» Read our latest here π
We could try, but it would be challenging to bump in the current state of the mempool (also bumping will work with anchor channels).
Email us in a few days if it is still stuck (contact@breez.technology), but i have a feeling that the longer you can wait, the better.
Ouch, apologies for the inconvenience...
Ffiw, we're not manually closing channels atm, so this was probably triggered by a stuck payment... Let's wait and see how it plays out.
Breez works with RoboSats, perhaps a temporary liquidity issue?
I see... I think his channels got forced close for some reason. Maybe something useful in the warning?
Sure thing. Apologies for the inconvenience, I'm sure we'll get to the bottom of this πβ€οΈ
Roy from Breez here. Not sure what happened to your friend, but sats can't just disappear. If you sent an on-chain transaction and the swap failed, they should be refunded in Breez.
Please ask them to reach out to our support and we'll follow up: contact@breez.technology.
Ah? Breez is non-custodial and requires less trust than Phoenix atm.
We have Kotlin bindings... Feel free to reach out if you need any help from us
We are planning to support NIP-07 and NIP-46 πͺ
Breez SDK ftw. We're missing async payments support, but it's coming.
Just a small nit: not switching, adding π We are planning to maintain the "node on device" option as well.

