You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I call my withdraw extension with a testnet invoice, I still receive a 200 ok status response. In my opinion, this should rather check the network of the invoice and return a 400 bad request. Because 200 ok indicates, that the invoice is valid, what isn't the case.
Same goes for handing over a mainnet invoice to a testnet instance.
Maybe there is some kind of misconfiguration in my lnbits instance, but I honestly doubt it.
Let me know if I can provide any logs or so for clarification.
The text was updated successfully, but these errors were encountered:
When I call my withdraw extension with a testnet invoice, I still receive a
200 ok
status response. In my opinion, this should rather check the network of the invoice and return a400 bad request
. Because200 ok
indicates, that the invoice is valid, what isn't the case.Same goes for handing over a mainnet invoice to a testnet instance.
Maybe there is some kind of misconfiguration in my lnbits instance, but I honestly doubt it.
Let me know if I can provide any logs or so for clarification.
The text was updated successfully, but these errors were encountered: