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.

Sign up for GitHub

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

Jump to bottom

Many trades produces multiple address entry in Send Funds tab and incorrect btc balance #3451

Closed
beingindot opened this issue Oct 23, 2019 · 5 comments
Closed

Many trades produces multiple address entry in Send Funds tab and incorrect btc balance #3451

beingindot opened this issue Oct 23, 2019 · 5 comments
Labels
an:investigation in:gui in:wallet was:dropped

Comments

@beingindot
Copy link
Contributor

[How to reproduce]

  1. Start Alice
  2. Perform many btc trades so that btc balance distributed within the wallet
  3. Distribute btc within the bisq wallet.

[Expected Results]
List of address in Send Funds should be unique and btc balance should be real count.

[Actual Results]
List of address displayed one address with two entries.
BTC balance also reflected those two entries.

Screenshot from 2019-10-23 21-05-35
Figure 1. one btc address having two entries and btc balance also incorrect.

The issue was discovered during v1.2.0 testing
@beingindot beingindot changed the title Many trades wihtin bisq wallet produces multiple same address entry and incorrect btc balance Many trades produces multiple address entry in Send Funds tab and incorrect btc balance Oct 23, 2019
@chimp1984
Copy link
Contributor

Can you make a spv resync at settings/network?

@beingindot
Copy link
Contributor Author

did that. but no change in listing and balance.

@freimair freimair mentioned this issue Oct 31, 2019
Closed
@beingindot beingindot mentioned this issue Nov 8, 2019
Closed
@beingindot
Copy link
Contributor Author

investigating to find the reason.

@beingindot beingindot mentioned this issue Dec 9, 2019
Closed
@stale
Copy link

stale bot commented Feb 12, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the was:dropped label Feb 12, 2020
@stale
Copy link

stale bot commented Feb 19, 2020

This issue has been automatically closed because of inactivity. Feel free to reopen it if you think it is still relevant.

@stale stale bot closed this as completed Feb 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
an:investigation in:gui in:wallet was:dropped
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@freimair @chimp1984 @beingindot