boltz-backend

boltz-backend copied to clipboard

add `boltz-cli ban `

maybeast

- TLS - some kind of authentication (macaroons?)

michael1011

Move to swap failed, invoice expired state immediately when invoice expired

1

Currently one sees this state when on-chain tx is not confirmed yet but invoice already expired:  Only realized this because of a user report, couldn't "download...

armurbalda

https://github.com/BoltzExchange/boltz-backend/pull/478 implemented batched normal swap claims via *script path spends*. Since batching is preferred when volume is high, we want to bring Taproot's privacy features and efficiency to batched claims...

kilrau

jackstar12

Increase CLTV Buffer

1

Let's check if we can increase for all after most switched to Taproot Swaps

kilrau

Batching Ideation

3

So there is the option for generic loop-style batching vs a liquid specific batching maybe even the option to batch using the pegin mechanism for very high-value pegins that we...

kilrau

Allow optionally to increase Boltz miner fee for lockup transaction

8

As per [comment below ](https://github.com/BoltzExchange/boltz-backend/issues/326#issuecomment-1651683088) we settled on only allowing users to optionally **increase** miner fees for lockup. Backend should add a new optional parameter to `/createswap` to allow for...

armurbalda

## Background Inspired by the [Breez idea of signing payments within mobile notification device compute time](https://sdk-doc.breez.technology/guide/payment_notification.html) and [Aqua](https://aquawallet.io/)'s desire to enable "Receive to [email protected]" Lightning Addresses, we are exploring the...

kilrau

Covenants: Trustless Refunds for Chain Overpayments

1

## Goal A Boltz API client should only be able to claim the previously agreed upon swap amount, if a user accidentally overpays. Client can then throw "you overpaid, enter...

kilrau