to all who use the Sparrow wallet and maybe have some unanswered questions about some settings or cofiguration with e.g. Bitcoin core, i found a very helpful website here and would like to share it with you now.
on this website you can watch different yt-videos, which can be interesting for everyone.
https://www.southernbitcoiner.com/sparrow-guides/
Topic: Sparrow wallet update 1.7.3 (Read 328 times)
I recently installed the Sparrow update 1.7.3, verified the PGP key, but my antivirus package started going crazy when I tried to sign a transaction, quarantining all the .tmp files. Is anyone else having this issue?
There are some antivirus software that are not compatible with some other softwares. If the antivirus is in the system and and you are installing another software or proggramme, the antivirus will detect the software as a virus and quarantine some the files in the software and delete some which will make the software not to work well. The antivirus that causes such problem in most time is Avast Antivirus and Norton Antivirus. Though I am using the mobile version of the Sparrow Wallet and it is doing well and you can connect bitcoin core to the wallet when you click on UTXOs and start your transaction.
Have you checked the Sparrow logs? Open Sparrow and go to "Help" -> "Show Log File".
I would also try shutting down Sparrow, unloading the wallet named "Sparrow" in Bitcoin Core, shutting down Core, deleting the "Sparrow" wallet folder from the Core directory, and then restart Core and then Sparrow.
I would also try shutting down Sparrow, unloading the wallet named "Sparrow" in Bitcoin Core, shutting down Core, deleting the "Sparrow" wallet folder from the Core directory, and then restart Core and then Sparrow.
Thanks for response.
Let me extend.
The problem pursues if Ledger nano s (or s+) is connected.to Sparrow.
When relevant files are deleted from Sparrow's folders (hwi and wallets) client connects to Bitcoin core in a moment.
Standard BIP-39 wallet created by Sparrow works properly.
UPD. 11.05.23: Issue resolved. The key was in outdated firmware and bitcoin app of my ledger nano. After updates Ledger+Sparrow+Bitcoin Core is working as it should be. It took me two days to get how to resolve the connectivity problem, shame of me.
Have you checked the Sparrow logs? Open Sparrow and go to "Help" -> "Show Log File".
I would also try shutting down Sparrow, unloading the wallet named "Sparrow" in Bitcoin Core, shutting down Core, deleting the "Sparrow" wallet folder from the Core directory, and then restart Core and then Sparrow.
I would also try shutting down Sparrow, unloading the wallet named "Sparrow" in Bitcoin Core, shutting down Core, deleting the "Sparrow" wallet folder from the Core directory, and then restart Core and then Sparrow.
Does anyone have problems with Sparrow connection to Bitcoin Core node?
my machine runs both Core 24.0.1 and Sparrow 1.7.6 but connectivity between them is painful.
A very rare attempt to connect ends in success. Most time Sparrow and node are in disconnected state.
Node has been properly configured to respond to RPC requests.
As I see the connectivity problem is in Sparrow itself as theother client (Spectre) which I use to connect to the same node does it like a charm.
my machine runs both Core 24.0.1 and Sparrow 1.7.6 but connectivity between them is painful.
A very rare attempt to connect ends in success. Most time Sparrow and node are in disconnected state.
Node has been properly configured to respond to RPC requests.
As I see the connectivity problem is in Sparrow itself as theother client (Spectre) which I use to connect to the same node does it like a charm.
That's reassuring, thanks.
I did, and I was able to sign no problem. It just alarmed me that maybe there was some malware in the wallet update.
Unfortunately, that's not something that anyone can say for sure. You said you verified the signatures, which means that the newest update was signed by the right person or people. What was signed is something completely different though.Generally, there shouldn't be a reason to worry. Anti viruses have in the past tagged software wallets as malware-infected. We have all read about it. Even Electrum and Bitcoin Core has been tagged as such.
That's awesome, thank you.
Thanks all. I'm using Avira AV
Then it definitely a false positive, unless the Sparrow.exe is fake.Quote
Just updated mine to test and there's no detection when signing transactions.
Which ".tmp" files are those?
The ones in appdata local temp folder which starts with "+JXF..." or the "hwi..." in Sparrow's data directory?
Because the former are most likely related to Sparrow's custom fonts while the latter is needed to connect your hardware wallet.
It's the hwi files. Which ".tmp" files are those?
The ones in appdata local temp folder which starts with "+JXF..." or the "hwi..." in Sparrow's data directory?
Because the former are most likely related to Sparrow's custom fonts while the latter is needed to connect your hardware wallet.
You can add an exception to hwi folder since the .tmp file may periodically change.
You can exclude it in "Avira's setting->Security->Protection Options->Real-time protection->Excluded folders".
Click "Exclude folder" and in Folder: type %appdata% (enter) to directly go to your 'appdata/Roaming' directory, open "Sparrow" folder and then 'select folder' "hwi".
As convenience, Avira will also add it to its Virus Scanner's folder exclusion.
Thanks all. I'm using Avira AV
It's the hwi files.
I did, and I was able to sign no problem. It just alarmed me that maybe there was some malware in the wallet update.
Good suggestion, thanks.
Quote
Just updated mine to test and there's no detection when signing transactions.
I'm using Avira AV in the machine where Sparrow is installed.
Which ".tmp" files are those?
The ones in appdata local temp folder which starts with "+JXF..." or the "hwi..." in Sparrow's data directory?
Because the former are most likely related to Sparrow's custom fonts while the latter is needed to connect your hardware wallet.
I'm using Avira AV in the machine where Sparrow is installed.
Which ".tmp" files are those?
The ones in appdata local temp folder which starts with "+JXF..." or the "hwi..." in Sparrow's data directory?
Because the former are most likely related to Sparrow's custom fonts while the latter is needed to connect your hardware wallet.
It's the hwi files.
Quote
Try turning off your antivirus software while working with Sparrow wallet and see if that helps.
I did, and I was able to sign no problem. It just alarmed me that maybe there was some malware in the wallet update.
Quote
If excluding doesn't work I suggest switching to another AV like Kaspersky is a better choice because windows defender has many false negative detections it would be better to disable it and switch to AV which has updated database.
Good suggestion, thanks.
I recently installed the Sparrow update 1.7.3, verified the PGP key, but my antivirus package started going crazy when I tried to sign a transaction, quarantining all the .tmp files. Is anyone else having this issue?
I've to seem like this when ppl use SEP, what you have to do is just "Disable rescanning" and "Do nothing" on New Virus Definitions Arrive. 
I recently installed the Sparrow update 1.7.3, verified the PGP key, but my antivirus package started going crazy when I tried to sign a transaction, quarantining all the .tmp files. Is anyone else having this issue?
There is usually an option to restore these files in the antivirus quarantine settings if the status is only quarantined and not deleted permanently. And then, configure the antivirus to ignore the hwi folder: https://sparrowwallet.com/docs/faq.html#where-does-sparrow-store-data.
I've experienced almost the same thing, but on Bitcoin Core.
If excluding doesn't work I suggest switching to another AV like Kaspersky is a better choice because windows defender has many false negative detections it would be better to disable it and switch to AV which has updated database.
Based on the link posted by Mitchel its hwi with a .tmp extension its under this folder below
Which ".tmp" files are those?
The ones in appdata local temp folder which starts with "+JXF..." or the "hwi..." in Sparrow's data directory?
The ones in appdata local temp folder which starts with "+JXF..." or the "hwi..." in Sparrow's data directory?
Based on the link posted by Mitchel its hwi with a .tmp extension its under this folder below
Code:
C:\Users\USER\AppData\Roaming\Sparrow\hwi
Try turning off your antivirus software while working with Sparrow wallet and see if that helps. Disable real-time protection, the firewall, and whatever else there is. If you are on Windows, your OS might automatically activate Windows Defender once it notices that no other AV software is operational. You may or may not have to do the same with Windows Defender.
What antivirus are you using software are you using?
What antivirus are you using software are you using?
-snip- but my antivirus package started going crazy when I tried to sign a transaction, quarantining all the .tmp files. Is anyone else having this issue?
Just updated mine to test and there's no detection when signing transactions.I'm using Avira AV in the machine where Sparrow is installed.
Which ".tmp" files are those?
The ones in appdata local temp folder which starts with "+JXF..." or the "hwi..." in Sparrow's data directory?
Because the former are most likely related to Sparrow's custom fonts while the latter is needed to connect your hardware wallet.
I can see one issues that could be relevant to this: https://github.com/sparrowwallet/sparrow/issues/815
Don't think you can do much about it except exclude the folders that contains said files, especially if you are certain you have a genuine version of Sparrow installed.
Don't think you can do much about it except exclude the folders that contains said files, especially if you are certain you have a genuine version of Sparrow installed.
I recently installed the Sparrow update 1.7.3, verified the PGP key, but my antivirus package started going crazy when I tried to sign a transaction, quarantining all the .tmp files. Is anyone else having this issue?
Jump to: