Just thinking out loud: you could make 2 input fields on the site: one with real addresses, and one where the user inputs funded addresses they don't own. If this is all handled client side, and all addresses are requested from the server (in no specific order), the "dummy addresses" can be ignored and only the requested addresses are shown. It wouldn't be perfect, but I think it can be called "improved privacy".
yes, i was thinking about something like that.
Everything done in JS is done client side. The problem is that on the client side users are making specific calls to sochain website. I cannot see what addresses you are calling when you use it, but sochain ofc does.
If I could somehow solve this privacy problem (with a solution like this one you mentioned), this solution could be also be implemented in SPV wallets for increased privacy.
Did Samourai wallet has a solution for this? Samourai is an improved privacy wallet, so maybe they already found a solution for this which I could implement in JS in this tool.
Thinking out loud as well
