pull down to refresh
0 sats \ 4 replies \ @aftermath 2 Apr \ on: Boltz AMA ⚛️🔁 AMA
- What are the biggest challenges you have faced while maintaining your Lightning nodes?
- What characteristics do you look for when selecting nodes to open new channels? Do you open channels at all or do you balance liquidity via swaps?
- Your nodes were accessible through the Tor network in the past, but not anymore, what has led you to change this?
- Wheeeere do we start... LND's bbolt database is a massive problem for large nodes like ours. Migration to postrgres was promised many years back and yet here we are still running on bbolt and regularly rebooting our node for database compaction. CLN's pay was absolutely borked until the debut of xpay just some months ago. Michael had to write our own pay plugin (called mpay obviously) to be even able to use our node for payments And we worked with Rusty and the team quite a bit to improve xpay. As of v25.02. it's usable.
- We almost never open channels, our gravity seems to be large enough so far that even large players like Binance open to us.
- As of recently, correct. We love Tor and continue serving our web app and API via Tor but Tor with Lightning is just not a great match. We witnessed so many payments getting stuck at a tor node on the route that, as harsh as it sounds, running a Lightning node on Tor is not doing anyone favors because of the unreliability of the Tor network.
reply
As of recently, correct. We love Tor and continue serving our web app and API via Tor but Tor with Lightning is just not a great match. We witnessed so many payments getting stuck at a tor node on the route that, as harsh as it sounds, running a Lightning node on Tor is not doing anyone favors because of the unreliability of the Tor network.
For now 😈 Keep an eye peeled on what is brewing in the kitchen https://github.com/el-tor
You will never get a clear response to that Q because otherwise everybody will start a swap service.
It's all about liquidity economics.
Nobody will give you the "secret" recipe.
reply