Content
@
https://warpcast.com/~/channel/walletbeat
0 reply
0 recast
0 reaction
polymutex
@polymutex.eth
Adding wallet data for transaction privacy. Currently only about ERC-5564 (stealth addresses); will add ๐ช๏ธ-type solutions later. ERC-5564 is very tricky to implement in a privacy-preserving way. No wallet gets it right today. https://github.com/walletbeat/walletbeat/commit/e667140f941a9eaf7e9bdc24b11697ed646f64b4
2 replies
7 recasts
16 reactions
polymutex
@polymutex.eth
Specific pitfalls to look out for: 1๏ธโฃ When ๐น๐ผ๐ผ๐ธ๐ถ๐ป๐ด ๐๐ฝ your stealth balance, does your wallet RPC provider learn the correlation between your stealth addresses? This defeats the purpose of stealth addresses, at least as far as that provider goes. Now you have to trust them & hope they'll never get hacked. 2๏ธโฃ When ๐๐ฒ๐ป๐ฑ๐ถ๐ป๐ด to a stealth meta-address, does a third-party learn the correlation between that meta-address and the generated stealth address you are about to send funds to? (eg. through an offchain resolver) If so, that provider now knows who you're sending funds to. 3๏ธโฃ When ๐๐ฝ๐ฒ๐ป๐ฑ๐ถ๐ป๐ด from your stealth balance, can you accidentally leave an onchain trail revealing that two of your stealth addresses belonged to the same user? Similar problem as "coin control" in UTXO chains.
2 replies
0 recast
6 reactions
Sebastian Bรผrgel
@scbuergel
When using stealth and non-stealth addresses: does your wallet use the same RPC provider and thus turn your IP address into a unique identifier?
0 reply
0 recast
1 reaction
