Check out one of the easiest & cheapest ways to do #LightningNetwork channel rebalances via Liquid swaps on #[1] with help from #[2]
⚡️🌊
Discussion
Where I can read (not watch) about it? Thanks! 🐶🐾🫡
You cab read about it here: https://blog.boltz.exchange/p/launching-liquid-swaps-unfairly-cheap
Cool, thanks! So from what I read, it’s not primarily helpful to routing nodes, and mainly for the rebalancing of inbound capacity on unspecified channel that happened to route to Boltz. Still good, but probably not what I was hoping for! 🐶🐾🫡
We are targeting routing nodes with this product, but the status quo is rather a proof of concept. Agreed!
What are you missing to make this useful for you?
Getting inbound liquidity for *specific* channel? Rn you manually would have to control the channel used for the outbound payment in the swap, but we are partnering with a node monitoring and rebalance autmation solution that connects a local daemon to your node doing this for you.
For getting outbound liquidity in a *specific* channel we still need to implement https://github.com/BoltzExchange/boltz-backend/issues/197
Eventually we want liquid swaps to be tightly controllable but fully automated via a local daemon connected to your node. No need to handle liquid/L-BTC.
That’s probably what I am missing, but I understand that it is yet too early. Full automation is most desirable result for this. If we could also use Liquid for all our channel needs (open/close) that would have been a dream. Thank you for providing detailed information and relevant links! 🐶🐾🫡
Woah… Rabbit hole incoming
✨🤩✨💜✨
Brutal Atomic Swap 💧🧡
I did this a bunch today with the Core Lightning on #[4] app.
Can’t say I fully understand what’s going on or was able to reproduce results reliably but it happened.
It finally freakin happened.
I got 10K inbound liquidy provisioned to my #Lightning node 😂