.merge+ 10331

Added

can anyone offer the use cases for a --restricted wallet-rpc? and/or give feedback for which things should be available for it in monero-project/monero #10378 - there is no custom 'allow_this_in_restricted_mode' for each method so its all or nothing

<o​frnxmr:xmr.mx> IMO i think read operations should be allowed, as well as store (a write operation). I would say that the only thing that should be read, is private keys. tx keys, proofs etc should be readable. I don't think its productive to lose all sync progress anytime the wallet is shut down

<o​frnxmr:xmr.mx> Currently the use case would, i think, be because you want to monitor outgoing txs. So a pseudo view-balance wallet

<o​frnxmr:xmr.mx> for the curent pr.. i would unrestrict store and get_tx_key. the latter aligns with 10271 reasoning (and get_*_proofs arent restricted either)

Ideally we would use a multisig wallet for that purpose, instead of having a hot wallet protected by --restricted, but, experimental and all that

<o​frnxmr:xmr.mx> Don't you have to sync key images with peers to see the outgoing txs on a musig?

OVK would help here ofc. I think im forgetting that with RINO you spent from their UI so they didnt need to sync? 🤔

.merge- 1378 1379

removed them until the discussion is resolved

typo?

.merge- 10378 10379

Removed

.merge+ 10397 10398

Added

<s​needlewoods_xmr:matrix.org> I'm open to unrestrict `store` and `get_tx_key` if there is strong support

<s​needlewoods_xmr:matrix.org> for `get_tx_key` I'd still like to hear jeffro256 s take, or from anyone who is qualified to asses potential security drawbacks

<s​needlewoods_xmr:matrix.org> for `store` there is ctrl+c to close the wallet which also stores it, meaning it's not impossible to store a restricted wallet, but you need to have direct access