search

michaelWuensch / BitBanana

Lightning Node Management for Android
https://bitbanana.app
MIT License
105 stars 11 forks source link

USD amount far more than actual amount #71

Closed HalFinneyIsMyHomeBoy closed 9 months ago

HalFinneyIsMyHomeBoy commented 10 months ago

It should be about $900, but it says much more.

signal-2024-01-22-122951_002

michaelWuensch commented 10 months ago

Oh, wow, strange. Just checked mine, it shows correcly when switching to dollars.

Which exchange rate provider do you use (it can be set in advanced settings)

And is tor turned on in your settings menu? Exchange rate requests are often blocked by cloudflare when done over tor. But normaly this can lead to old exchange rates not to incorrect ones. Still you could try to deactivate tor in the settings for a few minutes and see if it fixes the problem.

michaelWuensch commented 10 months ago

@HalFinneyIsMyHomeBoy I can also see that the sum of your account balance details does not even match your over all balance at all. 🤔 What if you have sats as your primary currency... does the sum match then?

HalFinneyIsMyHomeBoy commented 10 months ago

I apologize for the late reply, I switched the exchange rate provider to coinbase and that seems to have fixed that.

HalFinneyIsMyHomeBoy commented 9 months ago

Also, in regards to the incorrect sat balance, I recently closed all 3 channels on my Umbrel node (it was experimental anyway) The wallet still said I had a balance on LN, I uninstalled LND node from my Umbrel, reinstalled it and recovered with my seed.

Took a day or so to re-scan the blockchain, but after reconnecting BitBanana to my node, the correct sat and USD appears now.

Not sure if any of this info helps, but it's possible it had something to do with my Umbrel node.

michaelWuensch commented 9 months ago

I am closing the issue now. I checked the code and I basically display whatever lnd returns. I cannot reproduce it and have the suspicion something weird was going on with your node. Thanks for the info though! In case you experience this again or someone else has a similar issue, please reopen the issue.