transaction ID deleted
This is the transaction ID that I sent from my phone wallet to wasabi wallet.
It got more than 6 confirmations, but the amount is not showing in the wallet.
So, I restarted the Wasabi wallet, and the transaction was removed from the history.
How can I find my coin back??
A clear and concise description of what the bug is.
If applicable, add screenshots to help explain your problem.
Please consider your privacy, before completing this section.
Example: Ubuntu 16.04
Please consider your privacy, before completing this section.
You can find the log file by opening it from the main menu: File/Open/Logs File or File/Open/TorLogs File.
Which wasabi release are you using? Where did you download it from?
You can figure out which version you are using from the main menu: Help/About or with command line: wassabee --version.
Is your wallet connected to the backend?
Did your wallet finish downloading filters?
Okay I updated the wallet and received the transaction. But the coin that was already on the wallet disappered.....
Please be careful when publishing a transaction ID and attributing it to your self, now everyone knows that your GitHub account [although it's a fresh identity] has more than 1.8 bitcoin... Consider mixing your coins so to obfuscate your future transaction history.
Was your wallet opened when the transaction was sent? Because Wasabi builds it's own mempool, and you only receive unconfirmed transactions when you are online. But as soon as the transaction is confirmed, even when you are offline, you should see it when you open the wallet next time.
It might also be the "spend issue", which is fixed in version 1.1.10 and later, that might be the reason your coins changed after the update. The correct state will be shown on the latest version.
Thank you for the tip. I deleted the transaction ID.
The transaction got 21 confirmation when I checked it on the insight, so I restarted the wallet with the latest version and it disappeared again. How many confirmation do we need to see on the wallet?
hi , i have same problem my balance the transaction don't show anymore in history and balance...
How many confirmation do we need to see on the wallet?
If your wallet was open (online) when the transaction was sent you should see it immediately, if it was not then after 1 confirmation you should be able to see it.
there are 19 confirmation and balance don't show any update it show before confirmation but now is like dissapear
same problem here and now on the insight the receiving address that wasabi provided is unparsed address.
is it because of spend issue????
exactly the same thing happened to me just few minutes ago, I still can't see the tx, the tx have already 10 confirmations
I'm using wasabi wallet v1.1.10.1 on ubuntu
It's very weird that 3 users got the same issue at almost the same time, do you have some guide to recover the funds with the seed?
I restarted wasabi many times and it's not changing anything, it shows me the wallet's history but doesn't show the last tx.
i try also to recover the wallet and same problem
Update: I try to recover the wallet with the seed and the same thing, I can see the tx history but can't see the new tx
After 13 confirmations I finally see the tx, terrible UX
The filters got stuck. I restarted the server, the issue is solved. The underlying issue is still there why the filters got stuck.
same here the problem solved. the filter was stuck.
problem fixed also for me
Nice to hear that everything is working as expected now.
Closing this issue in favor of https://github.com/zkSNACKs/WalletWasabi/issues/3017
This is yet another example why it is not good [though currently necessary] to rely on the zkSNACKs server for filter generation and service... This shows how important it is to continue the work on Bitcoin Core integration, and push for BIP157 activation!
I'm glad all the user issues got resolved now, and hope we find a proper fix to the server issue asap.
Most helpful comment
The filters got stuck. I restarted the server, the issue is solved. The underlying issue is still there why the filters got stuck.