.merge+ 10753 10754 10756 10757

Added

done

.merge+ 10759

Added

ok, #monero channel is having a rather heated debate, so my question got buried there, so I will ask here. The question should be relevant enough, since it's about the monero-wallet-cli.

<ofrnxmr:xmr.mx> whatsup?

I was looking at the monero-wallet-cli documentation and tweeking some settings, and, as far as I understand, `print-ring-members` simply shows more information, but what about `store-tx-info` and `track-uses`? What do these two options entail? The first one relatively easy to understand -- it stores extra information, which would, I guess, be locally discarded otherwise, and probably shouldn't

be exposed -- except where the data is being stored. Is it in the wallet file or somewhere else?

For the latter one, a user actually gave me a hint on #monero about it possibly being for tracking "in which tx [my] outputs were used as decoys".

That would also be handled locally, no? Possibly stored in a log / wallet file?

track-uses just saves which txes use one of your ouputs when it sees such a tx. That info is saved to the wallet cache file.

Can't recall what exactly it saves. Could be just height, since the output it's used for is a timeline based on heights.

Mostly tourist information really.

moneromooo: Thanks for the explanation.

moneromooo: What about the `store-tx-info`, though? I somewhat understand what it saves, but do you know where it saves it? The help-command output mentions tx secret keys, so it is not really harmless information.

But it is one of the defaults, so I guess it is handled correctly (encrypted by the wallet password, perhaps).

Can't recall what this does, sorry.

Wallet stuff is saved with chacha20 though.

And yes, the wallet password to derive a key.

Neat.

So all the extra info provided by `store-tx-info` and `track-uses` should be protected as part of the encrypted wallet file.

And no extra, specific requests are made.

If I got it all correctly.

`print-ring-members` also seems just to display temporary data for the transaction, that is already being fetched on its own.