11:01:35 .merge+ 10753 10754 10756 10757 11:01:35 Added 11:07:16 done 17:59:04 .merge+ 10759 17:59:04 Added 19:53:04 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. 19:54:04 whatsup? 19:56:05 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 19:56:07 be exposed -- except where the data is being stored. Is it in the wallet file or somewhere else? 19:58:27 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". 19:58:56 That would also be handled locally, no? Possibly stored in a log / wallet file? 20:04:04 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. 20:05:03 Can't recall what exactly it saves. Could be just height, since the output it's used for is a timeline based on heights. 20:06:11 Mostly tourist information really. 20:23:16 moneromooo: Thanks for the explanation. 20:25:11 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. 20:25:43 But it is one of the defaults, so I guess it is handled correctly (encrypted by the wallet password, perhaps). 20:38:18 Can't recall what this does, sorry. 20:38:50 Wallet stuff is saved with chacha20 though. 20:39:07 And yes, the wallet password to derive a key. 20:43:44 Neat. 20:44:32 So all the extra info provided by `store-tx-info` and `track-uses` should be protected as part of the encrypted wallet file. 20:44:57 And no extra, specific requests are made. 20:45:03 If I got it all correctly. 20:46:27 `print-ring-members` also seems just to display temporary data for the transaction, that is already being fetched on its own.