<p><a href="https://medium.com/@nopara73/bitcoin-privacy-landscape-in-2017-zero-to-hero-guidelines-and-research-a10d30f1e034" rel="nofollow noreferrer">I conducted an extensive research</a> on the topic and to date the lightest weight wallet, that is resistant against network analisys is a <strong>full-SPV wallet</strong>.<br>
The structure of it is evident and some are already working on it, including me. This wallet would basically sync the headers and only download blocks from the creation of the wallet, and would store them in a pruned manner.  </p>

CC BY-SA 3.0
2017-02-08T16:32:15.423Z
2017-02-08T16:32:15.423Z
nopara73
<p>I am looking for an approach to build a privacy centric lighter weight wallet.<br>
By privacy centric I only mean: network observers should be unable to guess the addresses belongs to the same wallet.<br>
So querying information about addresses should be private.<br>
By light-weight I mean:<br>
1. Do not store hundreds of GB of data (a few is fine).<br>
2. Do not sync for ages. Should be finished within an hour maybe.<br>
The lightest privacy preserving approach I was able to find is pruning, what solves my first criteria, but not the second.<br>
BIP37 is not a good. (See: <a href="https://jonasnick.github.io/blog/2015/02/12/privacy-in-bitcoinj/" rel="nofollow noreferrer">https://jonasnick.github.io/blog/2015/02/12/privacy-in-bitcoinj/</a>)<br>
Do you guys have suggestions? (Or direct me to a better room to ask this question?)</p>

<privacy><spv><pruning>
Privacy approach for a light-weight wallet
nopara73
# Privacy approach for a light-weight wallet

(Asked by: username_0 on 2017-02-04)

I am looking for an approach to build a privacy centric lighter weight wallet.  
By privacy centric I only mean: network observers should be unable to guess the addresses belongs to the same wallet.  
So querying information about addresses should be private.  
By light-weight I mean:  
1. Do not store hundreds of GB of data (a few is fine).  
2. Do not sync for ages. Should be finished within an hour maybe.  
The lightest privacy preserving approach I was able to find is pruning, what solves my first criteria, but not the second.  
BIP37 is not a good. (See: <https://jonasnick.github.io/blog/2015/02/12/privacy-in-bitcoinj/>)  
Do you guys have suggestions? (Or direct me to a better room to ask this question?)

**Tags:** privacy, spv, pruning


---

## 1 answers

### Answer by username_0 on 2017-02-08. Score: 0 | Accepted answer

[I conducted an extensive research](https://medium.com/@username_0/bitcoin-privacy-landscape-in-2017-zero-to-hero-guidelines-and-research-a10d30f1e034) on the topic and to date the lightest weight wallet, that is resistant against network analisys is a **full-SPV wallet**.  
The structure of it is evident and some are already working on it, including me. This wallet would basically sync the headers and only download blocks from the creation of the wallet, and would store them in a pruned manner.


---

