jackstar12

same problem here

What about emulating the behaviour for wallets that dont support it? The base wallet could provide such implementation which would be overriden by wallet that support it. Something like: ```python...

> Especially since lnurlw/p from that wallet still work after deletion (right?).. where are those booked if only sats to active wallets are filtered.. a deleted wallet wouldnt work anymore

I considered this in https://github.com/lnbits/lnbits/pull/1816 aswell but didnt go for it as its used multiple times across multiple https://github.com/search?q=org%3Alnbits+NOT+repo%3Alnbits%2Flnbits+NOT+repo%3Alnbits%2Flnbits-legend-1+max_sat%3D&type=code so it would require a bunch of adjustments

You can do this by filtering on the `amount` field. An incoming payment has an amount greater than 0 - this can be filtered by `GET /api/v1/payments?amount[gt]=0` Would only return...

@ShahanaFarooqui yes I did. It doesnt need more changes since the api is the same for both lnd and cln and backwards compatible.

Just rebased: ``` Missing RPC commands in grpc: deprecations listsqlschemas parsefeerate commando-blacklist notifications batching check sql-template commando-listrunes commando-rune commando ```

Have you ever update boltz-client since then? It was an issue with the legacy api, which is used by RTL, but has been fixed since v2.3.8 https://github.com/BoltzExchange/boltz-client/commit/b2226a1eb938b26d669157f62e2cc32eb59821e0 If you ever...

to summarize / simplify a bit: - by default, use average of 3rd party providers - use boltz if all 3rd party fail

> We don't use fee estimations for successful swaps. The quote you approve when creating the swap is the amount you get. I don't see a use to validate things...