Silent Payments Wallet Support
One of the hardest things to keep up with in the Bitcoin space is keeping up with what wallets have deployed new features, what specific aspects have been deployed, and much more.
I’ll do my best to keep this page up to date, but if you see something that needs to be updated please submit a PR (use that “Edit this page on Github” button ->) or open an issue.
| Wallet | Github | Sending | Receiving | Privacy-preserving scanning1 |
|---|---|---|---|---|
| Cake Wallet2 | cake-tech/cake_wallet | |||
| BlueWallet | bluewallet/bluewallet | |||
| Silentium2 | louisinger/silentium | |||
| Dana Wallet | cygnet3/danawallet |
-
“Privacy preserving scanning” here denotes an architecture where no output information is revealed to the back-end server. While this is the only possible back-end approach for now, it’s very likely we will see future approaches that give the view key over to a back-end server to allow background sync, while sacrificing privacy of Silent Payments outputs to that third-party server. This field is a way that we can denote that in the future as-necessary. ↩︎
-
Silentium is a proof-of-concept and should be used with caution! From the developer:
↩︎ ↩︎This is an experimental project acting as a proof of concept for Silent Payments light wallets. Use at your own risk.