boltz-backend
boltz-backend copied to clipboard
BoltzExchange
Boltz Backend
We want to add a disclaimer that using https://api.boltz.exchange/swagger#/Chain/get_chain__currency__transaction__id_ https://api.boltz.exchange/swagger#/Chain/post_chain__currency__transaction involves trust in Boltz and that there are self-hosted and 3rd party solutions. We can only really push folks to...
also throw the exception of mpay so the rpc client can throw aswell
In line with lightning specs, we should fail normal swaps that have chain overpayments of more than >2x as this is very likely a user error. User's mostly fatfinger "one...
- Lightning only for prepayment - Main problem is what to do with existing integrations Related issues: https://github.com/BoltzExchange/boltz-backend/issues/278
We want to enable users that sent too much L-BTC in a Liquid-to-Lightning or Liquid-to-Chain swap to be able to claim refunds for the overpaid amount themselves using covenants. Refund...
To improve startup performance of mpay, the state of the plugin should be saved on disk on shutdown and loaded on startup. Avoids fetching payments from database and recalculating all...
The idea is to break our payment retry loops for offline Lightning wallets after X loops and only continue trying for another X loops if the websocket for the swap...
Add transaction details (id and hex if applicable) to the transaction related swap update events of submarine swaps