Sparrow Bitcoin Wallet

[dkbit98]

a new version was released today... the new 2.5.1 includes two bug fixes and an update.
you can see exactly what they are by visiting the following link: https://github.com/sparrowwallet/sparrow/releases/tag/2.5.1

It's interesting that Sparrow wallet is the first wallet that supports BIP375, that is sending Silent Payments with PSBT, that means that hardware signer can participate in constructing a transaction for sending to Silent Payment address.
That means that we should have more hardware wallets adding support for Silent Payments soon, and I hope Trezor and BitBox are going to be one of the first devices to do it.

[satscraper]

Latest Sparrow 2.5.2 release went to life

This release contains two very important bullets for Silent Payments. They are : "Improve verification of loaded PSBTs to warn on non-default sighash types" and "Improve BIP375 verification of precomputed SP outputs in PSBTs". These changes strengthen Sparrow’s ability to prevent funds from being sent to unspendable or suspicious scripts.

[nc50lc]

This release contains two very important bullets for Silent Payments. They are : "Improve verification of loaded PSBTs to warn on non-default sighash types" -snip-

I wonder why they quickly changed the wordings of this update from "...may be unsafe to sign" into moderate "Review this PSBT carefully...".

Since they do not allow signing with other sighash if you're using an SP Sparrow Wallet, perhaps it's an additional warning for another issue that should be called "unsafe".
E.g.: To warn their users so that they wouldn't sign a PSBT with "SighHash_None" or similar SigHash that could lead to stolen funds, but other SigHash aren't unsafe so the warning is toned down to "review it".
I actually mentioned this because I've seen threads that discussed that and there have been some real-world victims of that example scenario.
It's good that they've addressed that even if it's quite late and may be unintentional if the update is specific for Silent Payment.

[dkbit98]

I tried generating Silent Payment address with Sparrow wallet, but it was not working correctly for some reason.
I even tried connecting hardware wallet but Silent Payment address also didn't show and wrong hardware wallet was detected in SP menu.
Note that I used the latest Sparrow version 2.5.2, and I don't even own Trezor Model T device.

[satscraper]

I tried generating Silent Payment address with Sparrow wallet, but it was not working correctly for some reason.
I even tried connecting hardware wallet but Silent Payment address also didn't show and wrong hardware wallet was detected in SP menu.
Note that I used the latest Sparrow version 2.5.2, and I don't even own Trezor Model T device.

It’s strange that you tried to connectTrezor Model T to Sparrow Wallet in checking SP loop , because according to your own thread the only hardware wallet that supports SP right now is BitBox02 ^{and even that support is only partial}. So the outcome of your experiment was predictable.

Personally, I’m waiting for Foundation to add SP support to their products. Once that happens, I’ll try experimenting with pairing my Passport Core with Sparrow for SP transactions.

[dkbit98]

It’s strange that you tried to connectTrezor Model T to Sparrow Wallet

Like I said before, I never owned Trezor Model T, so Sparrow wallet is detecting this wrong, it's probably some bug.
I even tried generating Silent Payment addresses without any hardware wallet connection, but it was not working with Sparrow wallet.
There are no issues when I do it in Cake wallet.

[satscraper]

I even tried generating Silent Payment addresses without any hardware wallet connection, but it was not working with Sparrow wallet.

Strange. Mine generated the Silent Payment address properly. Unlike ordinary wallets, there should be only one Silent Payment address bound to each account in your wallet. If you need more, you must create additional accounts. Silent Payments are intentionally designed this way.

To see the generated Silent Payment address, you need to press the Receive button. It will show you the address and the corresponding QR code.

If you press the Addresses button instead, it will show nothing until you have received some funds to that address.

[Forsyth Jones]

the only hardware wallet that supports SP right now is BitBox02 ^{and even that support is only partial}. So the outcome of your experiment was predictable.

I own the Bitbox02 (the classic one, not the nova). AFAIK it only supports SP for sending. Does Sparrow with an integrated hardware wallet support SP? And what about a hardware wallet with partial SP support on Sparrow?

I could test it here with the Bitbox02 if I can find it.

[nc50lc]

I tried generating Silent Payment address with Sparrow wallet, but it was not working correctly for some reason.

Does it show anything interesting in "Help->Show Log File" menu? Anything related to the error.
Of course, refer to the timestamp exactly/close to when you seen that error or when you reproduced it.