walletbeat

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.

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

Contributor @ /walletbeat.

Censorship resistance requires privacy.

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.

Explore the EIPs / ERCs mentioned in this cast: