<r​brunner7:monero.social> SNeedlewoods: Finally found time to form an opinion about your questions. Left it on the PR, for better visibility.

<s​needlewoods_xmr:matrix.org> Appreciate it, you made good points, will wait before I change anything so others have a chance to share their opinions, don't want too much back and forth for the reviewers

<r​brunner7:monero.social> Thinking about it, the current inconsistent mix of restricted versus unrestricted is the best argument of having *simple* rules that are then simple to follow, and simple to check whether they are followed ...

<r​brunner7:monero.social> Hmm, just remembered that Feather Wallet stores a Polyseed as an attribute, to be able to show it again (you can't regenerate it from the private key), so that in theory an urestricted `get_attribute` call could be a problem. Sigh.

<s​needlewoods_xmr:matrix.org> ofrn suggested:

<s​needlewoods_xmr:matrix.org> > for the curent pr.. i would unrestrict store and get_tx_key. the latter aligns with 10271 reasoning (and get_*_proofs arent restricted either)

<s​needlewoods_xmr:matrix.org> libera.monerologs.net/monero-dev/20260403#c665331

<s​needlewoods_xmr:matrix.org> that would not fall under the simple "read only" category IIUIC

<s​needlewoods_xmr:matrix.org> This is just a problem if you create a wallet with Feather, close it, and then open that exact wallet file with `monero-wallet-rpc`!?

<r​brunner7:monero.social> Yes. It's probably something that we can neglect. But remember, on the other hand the security landscape is littered with failures that began with "Ah, no problem, that's impossible to exploit" :)

<o​frnxmr:monero.social> @rbrunner by " restrict keys on read-only wallet" are you including tx-keys here?

<s​needlewoods_xmr:matrix.org> True, maybe even other wallets will follow that approach. Do you have an idea how you would do it for monero-wallet-cli/rpc/gui?

<o​frnxmr:monero.social> the wallet would only have txkeys if the same cache file was used to create the tx, so i dont really see it as an issue. What can you really do with the txkey? Aside from read data

<s​needlewoods_xmr:matrix.org> that's how I understand it

<s​needlewoods_xmr:matrix.org> I mean, AFAIU `get_tx_key` would stay unrestricted with rbrunners simple approach

<r​brunner7:monero.social> Right, query of tx keys unrestricted, seems to me you can't really circumvent anything with them. If you have all the keys of all transactions, you still can't somehow restore the whole wallet with them, right?

<r​brunner7:monero.social> I think the way other wallets store the Polyseed, not as an attribute, but as part of the "account" info, is the more solid approach that maybe we should keep going forward

<r​brunner7:monero.social> But did not yet start to look into this closely.