Wallets supporting Silent Payments

[satscraper]

Does it really support Silent Payments?

The official site clearly states that Shakesco is MPC wallet ^{i.e., wallet that uses a Multi‑Party Computation scheme} which has nothing to do with Silent Payments.

I didn't install it or test it for myself, but I can clearly see pages on their website that are dedicated for Silent Payments.
I just tried installing Shekesco in my emulator but it won't open without g00gle account, so I don't have it.
This is certainly not a wallet I would recommend using, but my list is neutral.





Here is another proof they have some sort of silent payments:
https://github.com/shakesco/shakesco-silent

It seems you are correct. I have checked their FAQ

Meanwhile you  might want to add new wallet to the list which is Nunchuk, whose latest release made it partially compatible with Silent Payments. It’s only partial because it currently supports sending to Silent Payment addresses, but it still doesn’t support generating or scanning them.

This is the Nunchuk flavor for Android; the desktop version doesn’t seem to support Silent Payments yet.

[dkbit98]

Meanwhile you  might want to add new wallet to the list which is Nunchuk, whose latest release made it partially compatible with Silent Payments. It’s only partial because it currently supports sending to Silent Payment addresses, but it still doesn’t support generating or scanning them.

OK, I just added Nunchuk wallet in the list with partial support.
I was not following recent news from them, but this is certainly a move in good direction.
This year I am expecting to see more wallets adding support for Silent Payments, maybe even hardware wallets.

[satscraper]

This year I am expecting to see more wallets adding support for Silent Payments, maybe even hardware wallets.

I'm also expecting this feature to be added to Passport Core. They promised to implement it first thing in the morning after the first batch of Passport Prime units was shipped to customers. The shipment has recently begun, so I hope they follow through on what they promised. It would also be great if Sparrow proceeded with full support for Silent Payments. Having Passport Core with this feature along with Sparrow would finally make me ready to use it.

[cygan]

since the 4.0.-beta version of the great Ibis wallet, it is now also possible to send funds to silent addresses
this means there is another good mobile wallet that supports bip-352
@dkbit98 if you find the time, could you add this wallet to your list when you get a opportunity? thank you


https://github.com/aeonBTC/IbisWallet/releases/tag/v4.0-beta

[dkbit98]

since the 4.0.-beta version of the great Ibis wallet, it is now also possible to send funds to silent addresses
this means there is another good mobile wallet that supports bip-352
@dkbit98 if you find the time, could you add this wallet to your list when you get a opportunity? thank you

OK, I just added Ibis wallet to the list, thank you for suggesting
I haven't test this wallet yet but it looks promising what they achieved so far.
I am surprised that more wallets are not already supporting Silent Payments by now.

[satscraper]

I am surprised that more wallets are not already supporting Silent Payments by now.

And this is only half of the trouble. The real trouble is that the wallets claiming to support Silent Payments are not in hurry to implement full feature set. For example none of them support spending via PSBT, only a few can generate the necessary address formats, and very few implement privacy‑preserving scanning. Because of this, I still consider Silent Payments an experimental technique with no foreseeable timeline for mainstream adoption.

[dkbit98]

And this is only half of the trouble. The real trouble is that the wallets claiming to support Silent Payments are not in hurry to implement full feature set. For example none of them support spending via PSBT, only a few can generate the necessary address formats, and very few implement privacy‑preserving scanning. Because of this, I still consider Silent Payments an experimental technique with no foreseeable timeline for mainstream adoption.

I agree with that, but if Cake wallet can do it correctly, than other projects can follow that.
With more and more developers using different AI tools we care probably going to see more progress with Silent Payments in future.
I am really surprised that Trezor developers didn't release anything yet, especially knowing they history with BIP39 and SLIP39.

[cygan]

✂️
Somehow I missed this post, but now Spparow is added to the list.
If I understand correctly you can only send silent payments but not receivbe them with Spparow.

with the announcement of the new version today, the Sparrow wallet now also supports receiving silent payments.
this means that Sparrow now offers full support for sp

[dkbit98]

with the announcement of the new version today, the Sparrow wallet now also supports receiving silent payments.
this means that Sparrow now offers full support for sp

Great news!
I am updating information for Sparrow wallet, and I am also adding new BlindBit wallet that full supports Silent Payments.
BlindBit wallet is working on desktop computers for now, and it's still in experimental alpha stage.
It looks like I predicted correctly we are going to see more acitvity around Silent Payments 

[Forsyth Jones]

Bitcoin Core doesn't yet have a timeline for adding Silent Payments support, there are some open PR like this one: https://github.com/bitcoin-core/secp256k1/pull/1765

Since there are many technical details, I don't know the progress of the pull request.

I would really like to see this feature in Bitcoin Core, also remembering that Bitcoin Core took some time to add full Segwit support, I hope this changes in the coming months.

Oops, there's a PR that adds this functionality to the Bitcoin Core RPC (Receiving), currently with incomplete features, it will be interesting to follow: https://github.com/bitcoin/bitcoin/pull/32966

[LoyceV]

I would really like to see this feature in Bitcoin Core

From what I understand about Silent Payments, this feature would fit a full node very well. It requires scanning every transaction, and that's exactly what Bitcoin Core does already. I don't like trusting SPV wallets when it comes to privacy features, so I haven't used Silent Payments yet.

[Kruw]

Bitcoin Core doesn't yet have a timeline for adding Silent Payments support

There's a tracking issue: https://github.com/bitcoin/bitcoin/issues/28536

[Forsyth Jones]

I would really like to see this feature in Bitcoin Core

From what I understand about Silent Payments, this feature would fit a full node very well. It requires scanning every transaction, and that's exactly what Bitcoin Core does already. I don't like trusting SPV wallets when it comes to privacy features, so I haven't used Silent Payments yet.

I just created my first silent payments wallet on Sparrow Wallet v2.5.1, but it's not scanning/loading transactions. Furthermore, there's a red exclamation point icon next to the tab with my wallet name, blue-sp.

The transaction panel displays an error message stating that this server does not support silent payments.

My sparrow is connected to my Bitcoin Core full node, which has the -server and -txindex arguments enabled.

I don't understand why Bitcoin Core isn't scanning transactions for silent payments. What am I missing here?

I haven't transferred any funds to this wallet yet, it's newly created.

[BlackHatCoiner]

From what I understand about Silent Payments, this feature would fit a full node very well. It requires scanning every transaction, and that's exactly what Bitcoin Core does already. I don't like trusting SPV wallets when it comes to privacy features, so I haven't used Silent Payments yet.

What do you mean by "trusting SPV wallets"? The SPV server does not have to know your scan key. The entire point is that the scanning happens on the client side, the server simply sends you the tweak data for every block.

There's a tracking issue: https://github.com/bitcoin/bitcoin/issues/28536

If Bitcoin Core supports sending and receiving, then considering its RPC improves, Wasabi Wallet would improve significantly! Sending to a silent address is already supported, but without the ability to receive, it is doomed to have very minor adoption.

[TryNinja]

Still no news on a more mainstream wallet like Electrum supporting it?

A bunch of people I know use Electrum (me included), so I can't bother to use Silent Payments when so few wallets support it.

[Forsyth Jones]

Still no news on a more mainstream wallet like Electrum supporting it?

A bunch of people I know use Electrum (me included), so I can't bother to use Silent Payments when so few wallets support it.

Electrum is not among the wallets that support Silent Payments (SP).

Sparrow Wallet is the most recent wallet to launch with full support for Silent Payments, including receiving, while most on this list have added partial support (sending only).

To receive SP payments, a wallet doesn't need full support, the requirement is that the wallet has partial support for sending only. This helps ease adoption somewhat, unless the scenario changes.

-

I managed to use silent payments in Sparrow Wallet, in the settings, I've just need to change the Sparrow server to Electrum Frigate.

Add frigate.2140.dev as an SP-capable public Electrum server and auto-select it as required

[LoyceV]

What do you mean by "trusting SPV wallets"? The SPV server does not have to know your scan key. The entire point is that the scanning happens on the client side, the server simply sends you the tweak data for every block.

Based on this list, most Silent Payment wallets don't offer "privacy-preserving scanning".
It makes me wonder how much bandwidth it uses per week if the wallet supports the privacy-preserving scanning.

[satscraper]

And this is only half of the trouble. The real trouble is that the wallets claiming to support Silent Payments are not in hurry to implement full feature set. For example none of them support spending via PSBT, only a few can generate the necessary address formats, and very few implement privacy‑preserving scanning. Because of this, I still consider Silent Payments an experimental technique with no foreseeable timeline for mainstream adoption.

I agree with that, but if Cake wallet can do it correctly, than other projects can follow that.

I'm not sure whether Cake can handle it correctly. There have been some complaints relevant tot Silent Payments transactions within its community.

So I still consider Silent Payments an emerging technique that should be used very carefully until it becomes more polished.

I don't like trusting SPV wallets when it comes to privacy features, so I haven't used Silent Payments yet.

Yeah, Electrum‑style SPV clients sacrifice privacy, but clients like bitcoin‑safe, which use compact block filters, preserve it.

[nc50lc]

I'm not sure whether Cake can handle it correctly. There have been some complaints relevant tot Silent Payments transactions within its community.

Looks like the second one is the users' fault of reusing the derived TapRoot address instead of using the silent payment address.
But yeah, if it can't be solved by rescanning (which the user haven't tried yet),
Keeping track of the used address for new transactions should be implemented.

And the first one is already solved by the looks of it.

[satscraper]

Still no news on a more mainstream wallet like Electrum supporting it?

This is because Silent Payments features are much easier to implement in the descriptor‑based wallet than in wallet like Electrum, which uses the legacy key‑pair‑based architecture that would need drastic changes to support dynamic key derivation and other things required for Silent Payments technique. Sparrow handles this naturally through the relevant descriptors.