Besides having this issue intermittently,
https://github.com/zkSNACKs/WalletWasabi/issues/869#issuecomment-504731348
can't receive.
The addresses that get generated disappear from the Receive tab, and txs to them confirm, but they don't appear in the wallet. It remains 0 BTC, and nothing in History.
Tried sending from Samourai and Bitcoin Core so far.
In Bitcoin Core, receiving wasabi address was copy/pasted, instead of scanned.
Running version 1.1.5, installed from a deb file on Debian 9.9 in a Qubes R4.0 VM.
Tried reinstalling. Tried switching to Regtest and Testnet and back.
Recovering the wallet from seed also comes out empty.
The password checks out good in both the original and the recovered wallets.
What else to try?
initCCG
All 25 comments
In Wasabi, addresses disappear when a transaction is received. This prevents users reuse addresses inadvertently. So, if your address disappeared then Wasabi detected an incoming transaction. Wasabi needs to be fully synchronized in order to be able to display the full history and balance. For that reason you have to be sure your Wasabi is fully synchronized before trying anything else.
lontivero
on 23 Jun 2019
Is the receiving transaction confirmed already?
Sometimes there's an issue with displaying unconfirmed transactions...
MaxHillebrand
on 23 Jun 2019
Yes, from Bitcoin Core, the test send has 120+ confirmations, from Samourai more than 290.
The utxos are still unspent.
Wasabi says Backend is connected, Peers:8, and it was running for several days before we had time to do a test.
History is still empty, balance 0.
initCCG
on 24 Jun 2019
These are my two hypothesis:
- Wasabi is not synchronized. However, given Wasabi connects to the backend and also to the p2p network, I assume it is fully synchronized (it would be good if you could confirm it just to avoid assuming/guessing) or,
- You recover the wallet with the wrong seed. I think that it is possible that recovered the wallet with the wrong password and then, you are watching a totally different new wallet. This is easy to verify, just generate a new address and check if it is exactly the same address that you sent the money to. If it is not, then your recovered it with the wrong password.
lontivero
on 24 Jun 2019
Log file say
INFO Wasabi Synchronizer: Downloaded filter for block 582144.
The first address the recovered wallet generates is the same as the last unused address the original wallet generated.
We put the password from password manager. So, it's the same password.
initCCG
on 24 Jun 2019
Can you try it with the master branch? We fixed some inconsistency issues since. https://github.com/zkSNACKs/WalletWasabi#build-from-source-code
nopara73
on 24 Jun 2019
Sorry, we don't have room to install all this git and dotms in that VM.
Maybe can make a new VM when we have free time.
initCCG
on 26 Jun 2019
Then please wait for the next release. We'll get back to this issue with you to confirm that it's resolved.
nopara73
on 26 Jun 2019
Now we installed 1.1.6, and also created new wallet.
Same problems in all wallets: generated addresses disappear from Receive when we send them bitcoins, but don't appear in History or wallet balance.
Tor running, Backend connected, Peers: 8
Log keep repeating this error:
Downloaded filter for block 584879.
INFO MemPoolService: Start cleaning out mempool...
INFO MemPoolService: 560 transactions were cleaned from mempool.
WARNING UnobservedTaskException: System.AggregateException: A Task's exception(s) were not observed either by Waiting on the Task or accessing its Exception property. As a result, the unobserved exception was rethrown by the finalizer thread. (The peer has been disconnected) ---> System.OperationCanceledException: The peer has been disconnected
--- End of inner exception stack trace ---
---> (Inner Exception #0) System.OperationCanceledException: The peer has been disconnected<---
initCCG
on 11 Jul 2019
This is super strange. So the wallet knows about the transaction, but doesn't process it somehow. Does recovering your wallet in Electrum work?
Running version 1.1.5, installed from a deb file on Debian 9.9 in a Qubes R4.0 VM.
We won't be able to reproduce this setup easily. I hope the issue is not related. Virtualization in virtualization does not work.
Log keep repeating this error:
The log error is fine and unrelated. It's thrown by @NicolasDorier's NBitcoin, I've tried multiple times to catch it, but the code around there is pretty unique so I couldn't figure out where it's throwing.
nopara73
on 11 Jul 2019
@nopara73 the UnobservedTaskException don't come from NBitcoin. It comes from stuff throwing exception in methods with async void instead of async Task (typically async event handlers)
NicolasDorier
on 11 Jul 2019
If it keeps repeating the error, it might mean he is banned by nodes because broadcasting an invalid transaction.
NicolasDorier
on 11 Jul 2019
Hey @kixunil, can you [and do you have the time to] reproduce this setup? :)
Running version 1.1.5, installed from a deb file on Debian 9.9 in a Qubes R4.0 VM.
MaxHillebrand
on 11 Jul 2019
@NicolasDorier that exception comes frequently, like every few hours and it comes from NBitcoin.
It comes from stuff throwing exception in methods with async void instead of async Task (typically async event handlers)
async void crashes the system right away, it comes from not caught async Task.
nopara73
on 16 Jul 2019
@nopara73 do you have a stacktrace? I doubt it is that though.
NicolasDorier
on 17 Jul 2019
@NicolasDorier No more stack trace than published here. Why I think (know?) that this comes from NBitcoin, because the The peer has been disconnected string is not present in Wasabi, but it's in NBitcoin in 2 places:
nopara73
on 1 Aug 2019
@nopara73 both of them is because you send message while the peer is not connected.
There is still a very small chance that it happen even if you check IsConnected before, but that should almost never happen.
NicolasDorier
on 19 Aug 2019
Hello sirs, just update that user upgraded to 1.1.9.
Still same problem: balance is 0.
initCCG
on 23 Sep 2019
@initCCG Can you lower the dust limit in the settings, then restart? Maybe that's the issue?
nopara73
on 23 Sep 2019
And try to resync the wallet, I think the easiest way to do this for now is to switch to testnet in the settings, restart the wallet, switch to mainnet and restart again.
MaxHillebrand
on 23 Sep 2019
Ok, thank you sirs!
We'll advise the user to, but might take a while in case we have to send technical assistance to help.
initCCG
on 24 Sep 2019
We really should get #2031 merged into the next release...
MaxHillebrand
on 24 Sep 2019
It turned out to be the dust limit issue.
Might be useful to tell the non-technical users through some notification message that there is something in the wallet, but below dust limit.
initCCG
on 27 Nov 2019
We already lowered the dust limit, it's just we cannot force the users' existing defaults to be changed, so at least it won't be an issue with new users.
nopara73
on 27 Nov 2019
yahiheb
on 27 Nov 2019
Related issues
MaxHillebrand
路
3Comments
the-metalworker
路
3Comments
davterra
路
3Comments
kenny47
路
3Comments
gabridome
路
3Comments