Cryptocurrency wallets setup

perplexed

I am modeling my crypto wallets setup to get maximum privacy possible. I have no real experience with crypto. I know there are also other things to consider. Fiat to BTC exchanges will happen regularly.

"BTC" BTC wallet
"XMR exposed" XMR wallet
"XMR storing" XMR wallet

Wallet 3 is allowed to have transactions only with wallet 2.

Only one BTC wallet since it will be connected to my real life persona, therefore it is unnecessary to have different wallets to receive and withdraw BTC.

Solves:

from whom (only XMR to XMR)(*)
to whom (only XMR to XMR)(*)
how much (only of XMR to XMR)
where is it stored

(*) assuming the transaction counterparty will connect XMR wallets to my persona

Does not solve:

when (XMR nodes can determine when you receive money - source)

Does this make sense or there is a better setup?

raccoondad

perplexed You could run your own node and pipe your connection to there, or you could route it through Tor/VPN/whatnot, if you are concerned with a node knowing you had a transaction of some kind.

23Sha-ger

perplexed Does this make sense or there is a better setup?

There is, hardware wallet. I won't name any so it won't be considered as advertising.
But obviously it only makes sense when the amounts are > than the ~ of the monthly turnover.
This way you are not only keeping your wallet safe, but also solve the $5 wrench issue.

teezeh

perplexed I have no real experience with crypto.

Why are you using it then?

elbert

perplexed when (XMR nodes can determine when you receive money - source)

This affects only lightweight wallets. There are also "normal" wallets for Android like Cake Wallet or Monerujo. The way these work is they download the encrypted blocks from a remote node and scan for transactions themselves, so the view key is never shared with the remote node. This leads to somewhat longer sync times on the first run or if you haven't opened the wallet for a long time (although Cake Wallet recently implemented background sync, which mostly fixes this problem). Note: this doesn't solve all the problems with remote nodes, so if feasible I would still recommend you hosting your own node.