boltz-backend
boltz-backend copied to clipboard
BoltzExchange
Boltz Backend
Successor of https://github.com/BoltzExchange/boltz-backend/issues/455 (which is an undocumented temporary feature): we want to enable a more robust way of setting a "direct address" by storing it in the routing hints table...
Otherwise API clients have no way of knowing if it was set and recognized correctly
Letting Boltz construct a route via a specified channel when the channel id is specified would allow for creation of more custom channel opening and normal submarine swaps.
Substituting https://github.com/BoltzExchange/boltz-backend/issues/371, we want to make setting invoice memo and bip21 memo depending on referral key which solves the issues mentioned in #371 . current referral keys -> stay as-is...
- [ ] Still need to add more details on which values are needed for EVM refunds and best also an rpc call example for the emergency procedure how to...
* based on [taproot/musig2](https://github.com/BoltzExchange/boltz-backend/issues/337) * l-btc/btc only so far
- add unique error label to enable localization in web app - move amounts to separate section, have it separate from localization and enable denomination conversion in web app -...
Currently backend is unaware of refunds of normal swaps. It'd be nice to globally know which swaps were refunded by adding a `swap.refunded` final state for refundable normal swaps, meaning...
In a reverse swap with `prepayminerfee` set, two invoices are created, for the payment and for the mining fee. It is very common that one of the payments finds a...
Current bot-message ``` [mainnet]: Swap failed: onchain HTLC timed out ID: rkwzqr Pair: LTC/BTC Order side: sell Lightning amount: 0.00187779 BTC Invoice: lnbc1877790n1pwa9qzzpp584at9nc5f5c2ydnlrg25yq6dx5w8600tpg4vm0xw7hssldg3fazqdqqcqzpgxqrrss4dzfyc2lzyys2tzdmx6efqw58n9fmyznjxzcpsk5vxp73w7qtekrj8trqglqq8ew3uajhx6n27g03qmmh822eh4phvx5xthg0j2r9wqq3yfgaa ``` Desired rectification: `[mainnet]: Swap failed: onchain...