Avatar
Boltz - Non-Custodial Bitcoin Bridge
0c371f5ed95076613443e8331c4b60828ed67bcdefaa1698fb5ce9d7b3285ffb
Boltz is a non-custodial Bitcoin bridge built to swap between different Bitcoin layers while staying in full control. Support: https://support.boltz.exchange/hc/center
Replying to Avatar Bitcoin Signal

nostr:npub1psm37hke2pmxzdzraqe3cjmqs28dv77da74pdx8mtn5a0vegtlas9q8970 are you guys allowing newchannelsm? I am having trouble opening a channel to you on both the LND and CLN nodes.

Do you have any recomendations for opening a channel to you?

We accept new channels. For the minimal channel size of our nodes, you can check the https://amboss.space page

We just released Boltz Web App v1.2.1 πŸͺ²

- New BTC <-> Sats toggle

- Revert to sats as default denomination

- Fix false "invalid address" error

- Fix mobile refund file downloads

For the full run down check the release notes: https://github.com/BoltzExchange/boltz-web-app/releases/tag/v1.2.1

Today we shipped Boltz Web App v1.2.0 🚒

- Automatically detect & switch to Browser language

- Add Chinese language localization

- Improved refund file download as one simple step

- Clickable min/max amounts

- Improved behavior when jumping form landing page to /swap

- Swap Box Emped version for iframes

- Move important error messages into "Create Atomic Swap" button

- Default to BTC denomination for new users

- Many more fixes and improvements related to WebLN, LNURL, UI elements and more

For the full run down check the release notes: https://github.com/BoltzExchange/boltz-web-app/releases/tag/v1.2.0

Wait, are you somehow unsure if this was our fault? If so please DM swap or tx id or invoice. If our web app says the swap was refunded it was refunded.

> So in simple terms it is extremely expensive now.

Absolutely. That's why we have many folks exploring Liquid these days.

To clarify how network fees are charged: First thing to highlight is that every swap on Boltz consists of **two** chain transactions in order to allow for the non-custodial atomic swap flow: one transaction *locking* the coins on-chain and the second one *claiming* coins as part of the preimage release/unlock mechnism.

Now there we have two different directions where fees are paid differently:

Chain -> LN: lock transaction paid by the users wallet, you can set this fee freely in your wallet but need to make sure the transaction confirms before the ~24h swap timeout. The Network fee you see in our swap box is the one we charge is for our (one) transaction to *claim* the coins. The estimate is based on the expected transaction size*current mempool.space high priority fee. We need to use high priority since we have to make sure to not run out of money ending up with all our funds locked up in the mempool.

LN -> chain: here the network fee is roughly double from above because locking and claiming needs to be charged for. Locking from our side again is done using current mempool.space high priority fee, the claim fee is controlled by the client (our web app or boltz-lnd boltz-python, we have a couple of clients by now). Right now web app fixes the claim fee to mempool high prio too, but we want to allow for custom claim network fees in future. Opened an issue to not track it: https://github.com/BoltzExchange/boltz-web-app/issues/377

Replying to Avatar Ryu Santiago

Having an issue accepting this nostr:npub1psm37hke2pmxzdzraqe3cjmqs28dv77da74pdx8mtn5a0vegtlas9q8970 payment, and I presume it's due to not having channel liquidity.

Would there be an issue closing my current channel, and using this payment to create a new channel with more liquidity nostr:npub1xnf02f60r9v0e5kty33a404dm79zr7z2eepyrk5gsq3m7pwvsz2sazlpr5?

Yeah, we have a pending HTLC for your invoice since quite a while. nostr:npub1xnf02f60r9v0e5kty33a404dm79zr7z2eepyrk5gsq3m7pwvsz2sazlpr5 anything we can do make that one go through?

In the past days we are seeing the majority of @Liquid_BTC swaps in the 1k-10k sats range and practically no mainchain swap below 1 million sats.

Market doing its thing. Beautiful to watch πŸ€“

https://void.cat/d/3w3usS41rePJLq69ZA34TJ.webp

60 sats/vbyte to >400 sats/vbyte in less than 3h is the new normal. Prepare accordingly.

https://void.cat/d/Poiyw1sMmp4fwzhsp3LMGA.webp