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
Dean Pierce π¨βπ»ππ
@deanpierce.eth
Are there any wallets that provide the option of running a light client directly on your phone? The dependency on RPC providers has continued for way longer than I expected.
1 reply
0 recast
1 reaction
polymutex
@polymutex.eth
@ethos does this! But note that a light client doesn't solve for privacy nor availability, they only solve for trust. You still rely on an upstream RPC provider that your light client requests data from.
1 reply
0 recast
3 reactions
Dean Pierce π¨βπ»ππ
@deanpierce.eth
Ah neat, is there something special about the upstream RPC provider or can I point it to one of my own nodes?
1 reply
0 recast
1 reaction
