Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

False Transfer #2498

Open
Charliearlie1029 opened this issue Dec 11, 2024 · 1 comment
Open

False Transfer #2498

Charliearlie1029 opened this issue Dec 11, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@Charliearlie1029
Copy link

Charliearlie1029 commented Dec 11, 2024

To Reproduce

  1. Login (At first I had no issue but I did leave the application open for maybe 10 15ish minutes and came back to it)
  2. See all funds missing
  3. See notification showing transfer of all funds
  4. Panic
  5. Close then sign back in
  6. Everything back to normal

Expected behavior
Didn’t really expect to be missing everything and a notification showing a withdrawal of all my funds

Found in
Desktop v0.8.0-beta

Environment:

  • Platform: Desktop
  • Device: Desktop
  • OS: Windows 11
  • Browser: Using Komodo Application
  • Build mode: Release

Additional context
Seems to just be a visual issue. As stated before I did leave the application open for a bit but the notification saying there was a withdrawal was very worrying. After reopening everything thing is still there and fine.

@Charliearlie1029 Charliearlie1029 added the bug Something isn't working label Dec 11, 2024
@cipig
Copy link
Member

cipig commented Jan 13, 2025

this issue is for https://github.com/KomodoPlatform/komodo-wallet-desktop
and it happens because sometimes RPC nodes of the EVM chains return bad/wrong/outdated data for balance
there is no tx, the app simply shows a popup because it assumes that there was a tx... because if balance goes from x to 0, there must have been a transfer of the funds... but there was no transfer/tx... and app does not check if there was, it only checks balances and makes assumptions about txes (likely because fetching tx history from RPC nodes is much more expensive then fetching balance)
btw, with latest version it shouldn't happen that often, because i replaced one of the RPC nodes of the PLG20 chain with a better one... i personally didn't had the issue again since then

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants
@cipig @Charliearlie1029 and others