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

Network balance is not updated after sending transaction when network symbol is not ETH #12818

Closed
churik opened this issue Nov 15, 2021 · 2 comments · Fixed by #12843
Closed
Assignees
Milestone

Comments

@churik
Copy link
Member

churik commented Nov 15, 2021

Bug Report

Problem

Reproduced on BSC mainnet, can be tested on BSC testnetwork after merging #12810

Expected result:
will be updated when tx gets confirmed

Actual result:
no update until relogin or custom scan tokens

Reproduction

  1. create new multiaccount
  2. add BSC testnet (https://data-seed-prebsc-1-s1.binance.org:8545/ , 97 from here
  3. get Testnet Fund: https://testnet.binance.org/faucet-smart
  4. try to send it to any address and pay attention to balance update

Additional Information

  • Status version: nightly 15/11/2021
  • Operating System: Android, iOS
@churik churik added the bug label Nov 15, 2021
@churik churik added this to the Release 1.18 milestone Nov 15, 2021
@flexsurfer flexsurfer assigned flexsurfer and unassigned flexsurfer Nov 16, 2021
@flexsurfer
Copy link
Member

flexsurfer commented Nov 16, 2021

balance is not updated at all, even with pull to refresh, user has to relogin
it happens for faucet transactions as well

@rasom rasom self-assigned this Nov 18, 2021
@rasom
Copy link
Contributor

rasom commented Nov 22, 2021

History fetching is broken for those networks and that cause the problem with balances.

The issue on BSC testnet is that we can't fetch eth_getLogs for a range bigger than 5000 blocks, and that was a reason for an endless failing loop on status-go side. Although it is pretty simple to fix, later I figured later it wouldn't work on a main BSC network as it doesn't provide a historical data even for last 128 blocks (as it usually works on a regular ethereum node). That means we can't use our tx history scanning algorithm, also we will not be able to check recent history using it.

The only option we are left with is to show transactions which are sent from Status (or to use some third party api but no ethereum RPC) and provide a link to https://bscscan.com.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants