Jethro Grassie

Why is this in DRAFT status? It needs merging as the current doc is inaccurate.

> I am going to double check one thing with portable storage format: bool arrays. In c++ there is a specialization for `std::vector` which packs each bool value into a...

Much as I like the intent, I'm not sure it's a wise idea to have links in official (which is what they'd become if merged to this repository), man pages...

It _is_ documented in the wallet (see `help set`). The reason why it wouldn't be a _program_ runtime flag (which can be set via the config file or the flags...

There is another nuance: public vs private remote node. Using a private remote node (additionally connecting to it over TLS/SSH/Tor/i2p), is really no less secure than using a local node....

Also, the topic is wider than just where your keys exists when we're discussing privacy.

I think it's important owned/others and how you connect. Very quick draft of a breakdown could look like (where "secure" means "SSL/TLS/Tor/i2p"): |Type|Connection|Strength| |--|--|--| |Local full node|localhost|5| |Private remote node|secure|5|...

> I personally believe this should remain out of scope. But it's certainly a privacy consideration. I'm not so sure. Where keys are is only a fraction of the issue....

But if you really want to restrict this to "types" of wallets, then really we're talking wallet+local node, wallet+remote node, "openmonero type light wallet" I guess. The last wallet type...

I like @knaccc's breakdown if we're only talking wallet types, but still, this can lead to a false sense of security - the public/private remote distinction is missing and how...