pull down to refresh
31 sats \ 0 replies \ @boltz OP 8h \ parent \ on: Boltz AMA ⚛️🔁 AMA
https://canary.boltz.exchange, also check https://boltz.exchange/privacy. "Assume we keep all data we have forever" - you can't and shouldn't trust us if we said otherwise.
More automation options, improve the manual option via https://pro.boltz.exchange. And also make pro swaps useful with e.g. https://github.com/BoltzExchange/boltz-backend/issues/197
We are working on an Ark integration, which is probably the most significant thing we'll launch this year. Yes, we are profitable and we actually worked with Evan and the team to get sth up for them, but leaving it to them to announce ✌️
Absolutely, we got a BTCPay plugin that does exactly that. Read more about it here: https://blog.boltz.exchange/p/launching-the-boltz-btcpay-plugin (ignore the "Beta", it's a stable product by now).
Use another swap provider running Boltz backend that handles things differently via https://swapmarket.github.io
Or even better: launch your own swap service! All our code is Open Source: https://github.com/BoltzExchange.
Complaining doesn't change things, go and launch something! 🙌
We run a real world company with a legal entity.
This was a very pragmatic business decision. We were swamped with support tickets users reporting "Exchange A/B/C froze my account because I used onchain Bitcoin from a Boltz swap". We had to act to not make Boltz incompatible with regulated services.
Also: Boltz is not a privacy tool. Boltz is a tool to (atomically) swap between different Bitcoin layers. We respect users privacy by not requiring more data than strictly necessary to execute the swap, but Boltz is not to be confused with technologies that are meant to enhance your privacy, like coinjoins.
Great meme, but luckily we are not alone. There are more entities running Boltz backends by now (see e.g. https://swapmarket.github.io/) and then there is Acinq/Phoenix, Zeus and many more all build very solid payment infrastructure.
- 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.
100%. We feel the same as we use Boltz-powered wallets ourselves as daily drivers. We recently did some investigation with Bull Bitcoin and turns out much of the delay is on client side. So we are working with implementations to get these down. There is no technical reason why a Boltz Liquid swap for a merchant payment shouldn't complete end to end in sth like 5 seconds end to end.
Start with "21 Lessons: What I've Learned from Falling Down the Bitcoin Rabbit Hole" for a shorter intro and with "The Bitcoin Standard" for rethinking "money". Another great choice (albeit not a Bitcoin book) is "The Sovereign Individual".
Tl;dr: yes. The goal is to not "break compatibility" with regulated entities like major exchanges which our users deposit to. More: #926959